WME Place Interface Enhancements

Enhancements to various Place interfaces

这些是此脚本变更过代码的版本。 显示所有版本。

  • v2026.05.27.01 2026-05-27

    Update WMEPIE.js

  • v2026.05.15.00 2026-05-27

    Update WMEPIE.js

    Improved handling for the "Use alt city when primary has none" setting. It will now create the place with the street name as the primary street name on the segment. This was not always the case.

    Fixed bug in "Ignore PLRs & unnamed PR" logic. The ignore PLR & ignore unnamed PR settings were merged, but the code calling the function to find the closest segment was never ignoring unnamed PR. That setting is now applied to both as users would expect.

    Merge pull request #39 from fuji2086/master

    Update WMEPIE.js

  • v2026.04.20.02 2026-04-19

    Update WMEPIE.js

  • v2026.04.20.00 2026-04-19

    Update WMEPIE.js

  • v2026.03.31.00 2026-04-14

    make Open addr on create more reliable

    fix updateMessage

    Merge pull request #37 from dalverson/master

    make Open addr on create more reliable

  • v2026.03.28.00 2026-03-29

    perf: Merge PR #31 with enhancements - NavPointManager caching + UI/UX improvements

    Credits: Based on PR #31 by davidsl4 (WazeDev/WME-Place-Interface-Enhancements#31)

    This commit merges the performance optimization from PR #31 with critical bug fixes and UI/UX improvements:

    Core Feature (from PR #31):

    • Add NavPointManager class to cache venue navigation points
    • Eliminates expensive recalculations during venue movement (~500% performance improvement)
    • Removes unnecessary async/await keywords from synchronous functions
    • Refactor findClosestSegmentTurf to accept optional sdkInstance parameter for testability
    • Comprehensive JSDoc documentation for all modified functions and classes

    Bug Fixes Applied:

    1. Add null checks in drawNavPointClosestSegmentLines for navPoint and targetNavPoint

      • Prevents TypeError crash when no nearby road segments are found
      • Restores guard pattern from original code
    2. Fix argument copy-paste error in createPlace function

      • Changed findClosestSegmentTurf(searchPoint, settings.SkipPLR, settings.SkipPLR)
      • To: findClosestSegmentTurf(searchPoint, settings.SkipPLR, false)
      • Correctly passes false for skipPrivate (no SkipPrivate setting exists)
    3. Move NavPointManager initialization to init2() instead of module scope

      • Ensures SDK is fully initialized before event tracking begins
      • Aligns with established bootstrap pattern in codebase
    4. Fix variable naming in NavPointManager event tracking

      • Changed eventHandler variable name to eventRecord to prevent shadowing confusion
      • Maintains proper handler reference management in event tracking
    5. Fix settings not being respected in place creation logic

      • UseAltCity now only applies when UseCityFromClosestSeg is ON
      • Street is only set when UseStreetFromClosestSeg is ON
      • Each setting now properly controls its corresponding behavior

    UI/UX Improvements:

    1. PhotoViewer button responsive positioning (CSS media queries)

      • Repositions button based on screen size (1400px+, 1024px, 768px, mobile)
      • Stays visible on smaller viewports with dynamic bounds checking
      • Window resize handler prevents button from going off-screen
    2. All new places now open in Edit Mode (not View Mode)

      • Moved sdk.Editing.setSelection outside segment check
      • Now applies to ALL place types, regardless of closest segment
      • Consistent user experience for place creation
    3. Address editor auto-activates for all new places

      • Previously only for Residential with EditRPPAfterCreated setting
      • Now applies universally when setting is enabled
      • Renamed setting from "Open RPP address on create" to "Open address on create" for clarity
    4. Fixed settings logic for place creation

      • Each setting now properly guards its feature
      • EditRPPAfterCreated setting is now respected (address editor only activates when ON)
      • UseStreetFromClosestSeg/UseCityFromClosestSeg work independently

    Co-Authored-By: davidsl4

    Merge pull request #36 from JS55CT/master

    perf: Merge PR #31 with enhancements - NavPointManager caching + UI/U…

  • v2026.03.26.00 2026-03-27

    Guard against googlePlace selection type — sdk.Editing.getSelection() throws for new WME feature

    Waze recently rolled out Google Places as a visible, clickable layer in WME. Clicking a Google Place fires wme-selection-changed like any other selection, but sdk.Editing.getSelection() throws WMEError: Selection contains an unexpected object type googlePlace — because googlePlace exists in ObjectType but is not in the SDK's supported selectable types.

    Since the wme-selection-changed event payload is always undefined, there is no way to pre-screen the type before calling getSelection(). The fix is a single safeGetSelection() wrapper that catches WMEError and returns null for any unsupported type.

    Changes:

    Added safeGetSelection() helper (wraps sdk.Editing.getSelection() in try/catch, returns null on throw) Replaced all direct sdk.Editing.getSelection() calls throughout the script with safeGetSelection() Because every consuming callsite already guards on null or checks objectType === 'venue', no downstream logic required changes — clicking a Google Place now silently produces no selection from PIE's perspective and all features continue to work normally for regular venue selections.

    Merge pull request #34 from JS55CT/master

    Guard against googlePlace selection type — sdk.Editing.getSelection() throws for new WME feature

  • v2026.03.24.01 2026-03-24

    Update the require URL to point to the new version of the WME Utils - SDK Google Link Enhancer library, and comment out the debugger lines.

    Moving the SDK GLE link to always pull the most recent version via "https://greasyfork.org/scripts/569692/code/WME%20Utils%20-%20SDK%20Google%20Link%20Enhancer.js"

    Merge pull request #33 from JS55CT/master

    Update the SDKGLE URL to always pull the most recent version

  • v2026.03.18.01 2026-03-18

    Update WMEPIE.js

    Photoviewer tweaks

  • v2026.03.17.00 2026-03-18

    Fix: Category shortcuts always creating Residential Point Place (RPP)

    All place category shortcuts (menu items 1–12) were incorrectly creating Residential Point Places regardless of the configured category.

    Root cause: In createPlace(), the category parameter was being ignored — sdkCategory was hardcoded to resCategory instead of using the passed-in value. This was introduced during recent RPP-specific fixes.

    Change: createPlace() line 2272 — const sdkCategory = resCategory → const sdkCategory = category

    The fix is a one-line correction. All existing RPP-specific behaviour (nav-point insertion, EditRPPAfterCreated prompt) is unaffected, as those checks already reference the category parameter correctly.

    Merge pull request #30 from JS55CT/master

    Fix: Category shortcuts always creating Residential Point Place (RPP)

  • v2026.03.15.03 2026-03-17

    Update WMEPIE.js

  • v2026.03.15.02 2026-03-17

    Update version and enhance update message

    Updated version number and improved update message for clarity.

  • v2026.03.15.01 2026-03-17

    Update WMEPIE.js

  • v2026.03.15.00 2026-03-17

    Change category from RESIDENCE_HOME to RESIDENTIAL

    Updated category names and fixed a bug related to displaying place names for residential venues.

  • v2026.03.15.00 2026-03-15

    Restore Bootstrap SDK initialization (Phase 1.1 Step 2)

    Restored the modern Bootstrap pattern that was accidentally removed during backup restoration. This includes:

    • Updated version to 2025.04.10.01
    • Added Bootstrap @require directive
    • Added /* global bootstrap */ declaration
    • Changed IIFE from synchronous to async pattern
    • Replaced old synchronous bootstrap() function with SDK initialization using await
    • Updated init() function signature to receive sdk parameter
    • Verified syntax with node -c

    This enables the async/await pattern required for WME SDK integration and the Event System migration (Phase 1.1).

    Co-Authored-By: Claude Haiku 4.5 [email protected]

    Phase A: Migrate selection system to SDK APIs

    • Add SDK-native getSelectedFeatures(), hasPlaceSelected(), getSelectedPlace()
    • Replace 73 WazeWrap.getSelectedFeatures() calls with local wrapper
    • Replace 13 WazeWrap.hasPlaceSelected() calls with local wrapper
    • Replace W.selectionManager.unselectAll/setSelectedModels with SDK equivalents
    • Replace WazeWrap.hasMapCommentSelected() with SDK objectType check
    • Replace all .WW.getObjectModel() accesses with direct venue properties
    • Replace all .WW.getType() checks with SDK selection.objectType

    All getSelectedFeatures() calls now return SDK Venue objects directly. Selection helpers handle SDK.Editing.getSelection() API internally.

    SDK migration: Phases G-E complete

    Phase G: Add feature flags (PLACE_FILTER_SUPPORTED, AREA_HIDE_SUPPORTED, GEOM_EDITING_SUPPORTED, SPOT_ESTIMATOR_SUPPORTED, NAV_POINT_HOVER_SUPPORTED) Guard 8 functions that lack SDK equivalents

    Phase F: Remove loadScriptUpdateMonitor (bootstrap handles updates) Remove WazeWrap.Interface.ShowScriptUpdate Annotate change:mode workaround (no SDK equivalent)

    Phase D: Replace WazeWrap.Remote RetrieveSettings/SaveSettings with localStorage Replace WazeWrap.User.Rank() with sdk.State.getUserInfo() Replace W.prefs.attributes.isImperial with sdk.Settings.getUserSettings() Update WazeWrap.Interface.Tab to sdk.Sidebar.registerScriptTab() Update keyboard shortcuts registration (partial - phase D.2b deferred)

    Phase B: Replace W.model.venues.getObjectById with sdk.DataModel.Venues.getById Replace W.model.venues.on with sdk.Events.on Replace 3x UpdatePlaceUpdate calls with sdk.DataModel.Venues.updateVenueUpdateRequest Replace 4x UpdateObject calls with sdk.DataModel.Venues.updateVenue Mark UpdateObject for images, openingHours, categoryAttributes as deferred

    Phase E: Add pure-JS geometry helpers (lonLatToMercator, mercatorToLonLat, etc.) Replace WazeWrap.Geometry.ConvertTo900913 calls with lonLatToMercator Replace WazeWrap.Geometry.ConvertTo4326 calls with mercatorToLonLat Replace WazeWrap.Geometry.isGeometryInMapExtent with isInMapExtent Mark findClosestSegment and CalculateLongOffsetGPS for Phase E completion

    Version: 2025.06.03.00 Syntax: ✓ Valid Status: Ready for browser testing

    Complete remaining SDK migration fixes (Phase B continuation)

    Core improvements:

    • Added missing feature flag constants (PLACE_FILTER_SUPPORTED, AREA_HIDE_SUPPORTED, GEOM_EDITING_SUPPORTED, SPOT_ESTIMATOR_SUPPORTED, NAV_POINT_HOVER_SUPPORTED)
    • These were referenced in guards but never defined, now initialized in init()

    Phase B (Data Model) completions:

    • Replaced W.model.venues.objects iteration with sdk.DataModel.Venues.getAll()
    • Replaced 6 remaining W.model.actionManager.add(new UpdateObject(...)) calls with direct sdk.DataModel.Venues.updateVenue() method calls
    • Replaced 3 UpdatePlaceUpdate require+add patterns with sdk.DataModel.Venues.updateVenueUpdateRequest()
    • Fixed direct W.model.venues.objects[id] access to use getById() with null check

    Phase D (Selection/API) completions:

    • Replaced WazeWrap.hasSelectedFeatures() with (getSelectedFeatures().length > 0)
    • This works because Phase A wrappers now return SDK Venue objects directly

    Status:

    • Syntax validated: ✓
    • Remaining deferred operations (properly guarded):
      • W.map layer operations (Phase C - deferred)
      • Geometry editing operations (Phase G - guarded with GEOM_EDITING_SUPPORTED)
      • Place filtering (Phase C - guarded with PLACE_FILTER_SUPPORTED)
      • Nav point hover effects (Phase C - guarded with NAV_POINT_HOVER_SUPPORTED)
      • Spot estimator drawing (Phase C - guarded with SPOT_ESTIMATOR_SUPPORTED)
      • Area hide feature (Phase C - guarded with AREA_HIDE_SUPPORTED)

    Next: Browser testing to identify runtime issues with SDK API calls

    Version: 2025.06.04.00

    Co-Authored-By: Claude Haiku 4.5 [email protected]

    Fix critical SDK migration issues discovered during browser testing

    Issue 1: Missing Feature Flag Constants (ReferenceError)

    • NAV_POINT_HOVER_SUPPORTED was referenced in guards but undefined
    • All 5 feature flags now defined at module level (lines 220-225)
    • Accessible to all functions including event handlers

    Issue 2: DisplayPlaceNames using WazeWrap methods on SDK venues

    • venue.isPoint() → SDK helper function venueIsPoint(venue)
    • venue.isParkingLot() → SDK helper function venueIsParkingLot(venue)
    • venue.getOLGeometry() → SDK helper or direct GeoJSON access
    • venue.attributes.* → Direct SDK properties (venue.name, venue.categories, etc.)

    New SDK Helper Functions Added:

    • venueIsPoint(venue): Check if venue is a point (geometry.type === 'Point')
    • venueIsParkingLot(venue): Check if venue has PARKING_LOT category
    • venueGetCentroid(venue): Calculate centroid from GeoJSON geometry
    • venueToOLGeometry(venue): Convert SDK GeoJSON to OpenLayers geometry
    • isInMapExtent(geometry): Check if GeoJSON geometry is in current map extent

    DisplayPlaceNames Function Fixes:

    • Changed all venue.attributes.name → venue.name
    • Changed all venue.attributes.lockRank → venue.modificationData?.lockRank
    • Changed all venue.attributes.categories → venue.categories
    • Changed all venue.attributes.houseNumber → venue.houseNumber
    • Fixed isPoint/isParkingLot calls to use SDK helpers
    • Fixed geometry access to work with SDK GeoJSON format

    Syntax: ✓ Valid (node --check WMEPIE.js)

    These fixes address the immediate browser test errors:

    • TypeError: venue.isPoint is not a function
    • ReferenceError: NAV_POINT_HOVER_SUPPORTED is not defined

    Next: Reload WME and re-test place selection and place name display

    Version: 2025.06.04.01

    Co-Authored-By: Claude Haiku 4.5 [email protected]

    Fix DisplayPlaceNames null check and venue.attributes access

    Bug Fix: TypeError - Cannot read properties of undefined (reading 'categories')

    Issues Fixed:

    1. Added null check after getById - venue may be undefined/null

      • Line 2517: if (!venue) continue;
      • Prevents accessing undefined.categories or other properties
    2. Fixed remaining venue.attributes references

      • Line 2535: venue.attributes.categories → venue.categories (with null check)
      • Line 2536: venue.attributes.houseNumber → venue.houseNumber
      • Line 2536: venue.attributes.name → venue.name
      • Line 2536: venue.attributes.lockRank → lockStr variable (already defined)
    3. Ensured lockStr variable is reused in RESIDENCE_HOME branch

      • Consistent formatting across point and residence homes

    Syntax: ✓ Valid (node --check WMEPIE.js)

    Root Cause Analysis:

    • sdk.DataModel.Venues.getById() can return null when venue doesn't exist or isn't fully loaded
    • Previous code assumed venue was always defined, causing errors when accessing properties
    • Old WazeWrap .attributes pattern not properly converted in all code paths

    Test: Reload WME and toggle place names on/off

    Version: 2025.06.04.02

    Co-Authored-By: Claude Haiku 4.5 [email protected]

    Bulk replace SDK venue.attributes accesses throughout codebase

    SDK Migration Fix: Replace all remaining WazeWrap .attributes patterns

    Changes (Global Replacements):

    • venue.attributes.id → venue.id
    • venue.attributes.name → venue.name
    • venue.attributes.images → venue.images
    • venue.attributes.openingHours → venue.openingHours
    • venue.attributes.venueUpdateRequests → venue.venueUpdateRequests
    • ven.attributes.venueUpdateRequests → ven.venueUpdateRequests (PUR)
    • selected.attributes.categories → selected.categories

    Impact Areas:

    • Photo viewer integration (lines ~1630-1641, 1740, 1763)
    • PUR handling (lines 1662, 1680, 1836)
    • Image deletion (lines 1850, 1875, 1896)
    • Category management (lines 1939, 1943)
    • Opening hours formatting (line 2063)

    Rationale:

    • SDK Venue objects have properties at top level, not nested under .attributes
    • WazeWrap features had .attributes for backward compatibility with OpenLayers
    • These changes align with SDK data model structure
    • Fixes potential "Cannot read properties of undefined" errors

    Syntax: ✓ Valid (node --check WMEPIE.js)

    Test: All previous error cases should be resolved

    Version: 2025.06.04.03

    Co-Authored-By: Claude Haiku 4.5 [email protected]

    Fix area place selection - guard InsertGeometryMods and fix getOLGeometry calls

    SDK Migration Bug Fix: TypeError on area place selection

    Error:

    • TypeError: getSelectedFeatures(...)[0].getOLGeometry is not a function
    • Occurs when selecting area (POLYGON) places
    • In InsertGeometryMods event handler

    Root Cause:

    • InsertGeometryMods calls .getOLGeometry() on SDK venue objects
    • SDK venues don't have .getOLGeometry() method (WazeWrap API only)
    • Geometry editing features depend on W.geometryEditing which is unavailable

    Fixes Applied:

    1. InsertGeometryMods function (line 3201)

      • Added guard: if (!GEOM_EDITING_SUPPORTED) return;
      • Early exit prevents all geometry editing code from executing
      • Geometry editing deferred until Phase 3 SDK implementation
    2. onScreen utility function (line 1867)

      • Old: obj.getOLGeometry().getBounds()
      • New: isInMapExtent(obj.geometry) with SDK helper
      • Used by photo viewer zoom/pan functionality
    3. CenterOnPlace utility function (line 3957)

      • Old: venue.getOLGeometry().getCentroid()
      • New: venueGetCentroid(venue) using SDK helper
      • Added null safety checks

    Impact:

    • Area places now selectable without crashing
    • Geometry editing buttons/UI won't appear (guarded)
    • Photo viewing functionality preserved
    • Place centering functionality preserved

    Syntax: ✓ Valid

    Test Result Expected:

    • Select area place -> should not throw error
    • Place info displays normally
    • Geometry mods UI absent (guarded feature)

    Version: 2025.06.04.04

    Co-Authored-By: Claude Haiku 4.5 [email protected]

    Fix DisplayPlaceNames - replace W.map.getZoom with SDK API and remove redundant getById

    Feature Fix: Place names not displaying

    Issues Found:

    1. W.map.getZoom() is legacy API - should use sdk.Map.getZoomLevel()

      • Affects zoom level checks for displaying names
      • Points need zoom >= 17, areas need zoom >= 15
      • Legacy API call was failing silently
    2. Redundant getById call in loop

      • sdk.DataModel.Venues.getAll() already returns venue objects
      • Unnecessary second getById({ venueId: place.id }) was redundant
      • Loop simplified: iterate directly over venues

    Changes:

    1. DisplayPlaceNames function (line 2502+)

      • BEFORE: for (const place of sdk.DataModel.Venues.getAll()) { var venue = sdk.DataModel.Venues.getById(...) }
      • AFTER: for (const venue of sdk.DataModel.Venues.getAll()) { ... use venue directly ... }
    2. Zoom level checks (line 2516)

      • BEFORE: if ((isPoint && W.map.getZoom() >= 17) || (!isPoint && W.map.getZoom() >= 15))
      • AFTER: if ((isPoint && sdk.Map.getZoomLevel() >= 17) || (!isPoint && sdk.Map.getZoomLevel() >= 15))
    3. Related zoom checks already updated in other functions:

      • Line 2170: highlightedVenue zoom check
      • Line 2194: show/hide stop points based on zoom
      • Line 2225: checkConditions function

    Syntax: ✓ Valid

    Expected Result:

    • Place names now display when 'Show Place Names' is checked
    • Names appear at correct zoom levels
    • Lock levels display correctly when enabled
    • Points display at zoom 17+, areas at zoom 15+

    Test: Toggle 'Show Place Names' checkbox and zoom in/out

    Version: 2025.06.04.05

    Co-Authored-By: Claude Haiku 4.5 [email protected]

    Replace W.map.setCenter with SDK Map.setMapCenter API

    Additional SDK Migration Fix: Map centering

    Changes:

    1. CenterOnPlace function (line 3959)

      • BEFORE: W.map.setCenter([centroid.x, centroid.y], zoom)
      • AFTER: sdk.Map.setMapCenter({ lonLat: { lon: centroid.x, lat: centroid.y }, zoomLevel: zoom })
    2. Photo zoom navigation (line 1707)

      • BEFORE: W.map.setCenter(new OpenLayers.Geometry.Point(lon, lat))
      • AFTER: sdk.Map.setMapCenter({ lonLat: { lon: lon, lat: lat } })
    3. Map zoom control (line 1708)

      • BEFORE: W.map.getOLMap().zoomTo(17)
      • AFTER: sdk.Map.setZoomLevel(17)

    Impact:

    • Place centering now works with SDK API
    • Photo viewer zoom navigation works
    • Closest segment/nav point centering works

    API Reference:

    • sdk.Map.setMapCenter({ lonLat: { lon, lat }, zoomLevel?: number })
    • sdk.Map.setZoomLevel(level)

    Syntax: ✓ Valid

    Test: Center place when photo is clicked, zoom to place

    Version: 2025.06.04.06

    Co-Authored-By: Claude Haiku 4.5 [email protected]

    Add Turf.js library and geometry helper functions foundation

    Feature Foundation: Turf.js integration for geometric operations

    Changes:

    1. Added @require for Turf.js from CDN

    2. Added turf global declaration

      • Makes turf available throughout script
    3. Added 10 Turf helper functions:

      • createPoint(lon, lat) - Create GeoJSON point
      • createLineString(points) - Create GeoJSON linestring
      • createPolygon(rings) - Create GeoJSON polygon
      • geometryCentroid(geometry) - Get center point using Turf
      • geometryBounds(geometry) - Get bbox using Turf
      • geometryDistance(p1, p2) - Calculate distance in km
      • geometrySimplify(geometry, tolerance) - Simplify polygon/line
      • geometryBuffer(geometry, radiusKm) - Create buffer around geometry
      • pointInPolygon(point, polygon) - Point-in-polygon test
      • geometryLength(geometry) - Get linestring length in km
      • geometryArea(geometry) - Get polygon area in km²

    Architecture:

    • Keep OpenLayers geometries for layer display (no change)
    • Use Turf for all geometric calculations (replacements)
    • Convert between formats only when necessary
    • Gradual replacement: calculations→Turf, display→OpenLayers

    Next Steps:

    • Replace WazeWrap.Geometry operations with Turf equivalents
    • Replace OpenLayers geometric calculations with Turf
    • Keep OL.Feature.Vector and layer system as-is

    Syntax: ✓ Valid

    Version: 2025.06.04.07

    Co-Authored-By: Claude Haiku 4.5 [email protected]

    Phase 4 Step 1: Replace findClosestSegment with Turf.js implementation

    • Added findClosestSegmentTurf async function using SDK Segments API + Turf.js
    • Replaced 3 WazeWrap.Geometry.findClosestSegment calls:
      • drawNavPointClosestSegmentLines (line 2388)
      • findNearestSegment (line 2454)
      • createPlace (line 3014)
    • Made affected functions async: drawNavPointClosestSegmentLines, findNearestSegment, createPlace, doneHandler, endPlacementMode
    • Updated event handlers to use async arrow functions with error handling
    • Uses turf.nearestPoint for geometric calculations
    • Returns compatible object with closestPoint (OL.Geometry) and segment properties
    • Syntax validated with node -c

    Co-Authored-By: Claude Haiku 4.5 [email protected]

    Phase 4 Step 2: Replace calculateDistance with Turf.js implementation

    • Added olGeometryLength helper function to calculate LineString length in km
    • Converts OL geometry components array to Turf.js LineString for calculation
    • Replaced 2 WazeWrap.Geometry.calculateDistance calls:
      • PLSpotEstimatordoneHandler (line 3709) - parking spot estimation
      • PLSpotEstimatorCalibrationdoneHandler (line 3725) - calibration
    • Uses turf.length with 'kilometers' units
    • Handles errors gracefully
    • Syntax validated with node -c

    Co-Authored-By: Claude Haiku 4.5 [email protected]

    Phase 4 Step 3: Replace CalculateLongOffsetGPS with Turf.js implementation

    • Added calculateLongitudeOffsetMeters helper function
    • Uses turf.destination to calculate longitude offset accounting for Earth's curvature
    • Bearing 90 degrees for east/west offset calculation
    • Replaced 2 WazeWrap.Geometry.CalculateLongOffsetGPS calls:
      • Place copying for polygon places (line 4013)
      • Place copying for point places (line 4018)
    • Fixed typo: convertedCoords.long → convertedCoords.lon
    • Syntax validated with node -c

    Co-Authored-By: Claude Haiku 4.5 [email protected]

    Pushing out version of one of the SDK. See SDK Migration Record file for details

    Moved to GF hosted version of SDK GLE

    Adding geometry buttons for map comments

    Zero raw selector strings remain in usage — everything goes through WME_DOM now.

    What changed:

    WME_DOM object added at WMEPIE.js:68 with 14 named selectors covering venue panel, map comment panel, address edit, and map overlays 23 call sites updated across the file — from photo viewer (#showDiv) to geometry buttons (#AreaSize) to address RPP (.address-edit-view)

    adding Shadow DOM host elements houseNumber: '.house-number', sidebarAlert: 'wz-alert.sidebar-alert', searchAutocomplete: '#search-autocomplete', Usages become document.querySelector(WME_DOM.sidebarAlert), document.querySelector(WME_DOM.searchAutocomplete), and $(WME_DOM.houseNumber)[0].shadowRoot

    Version 1 of new UI

    Small updates for Photo Viewer possition button

    Change updateMessage for SDK support and design refresh

    Updated the updateMessage to reflect SDK support and interface design changes.

    Merge pull request #28 from JS55CT/master

    New SDK version + Updated UI

  • v2025.04.10.00 2025-04-10

    Bump version for GLE update

  • v2025.04.06.01 2025-04-06

    Update WMEPIE.js

  • v2025.04.04.02 2025-04-04

    Update WMEPIE.js

  • v2025.04.04.01 2025-04-04

    Update WMEPIE.js

  • v2025.01.24.00 2025-01-24

    GLE dupe link function restored. Bump version and update message

  • v2025.01.13.02 2025-01-13

    Update WMEPIE.js

  • v2025.01.13.01 2025-01-13

    Bump version again for GLE fix

  • v2025.01.13.00 2025-01-13

    Bump version

    GLE code has been disabled, per notification from Waze that they prefer we don't bring Google data into WME.

  • v2024.09.29.01 2024-10-12

    Update forum URL

  • v2024.09.29.01 2024-10-03

    Update WMEPIE.js

    Fix Tempkey typo

    Update WMEPIE.js

    Merge pull request #23 from willdanneriv/Patch-typo

    Patch typo

  • v2024.09.07.01 2024-09-07

    remove update message

  • v2024.09.07.01 2024-09-07

    Bump version to get latest GLE

  • v2024.07.11.01 2024-07-12

    Update WMEPIE.js

  • v2024.06.11.01 2024-06-11

    Update WMEPIE.js

  • v2024.04.23.01 2024-05-09

    Fix editRPPAddress

    Merge pull request #20 from fuji2086/patch-3

    Fix editRPPAddress

  • v2024.04.22.01 2024-04-22

    Update WMEPIE.js

  • v2024.03.20.01 2024-03-20

    Update WMEPIE.js

  • v2024.01.25.01 2024-01-26

    Update WMEPIE.js

  • v2023.01.25.01 2024-01-26

    Bugfix

    Fixed bug getting city from alt names

    Compatibility with v 2.206

    Merge pull request #18 from fuji2086/patch-2024.01.04

    Bugfix

  • v2023.12.01.02 2023-12-03

    Update WMEPIE.js

  • v2023.12.01.01 2023-12-03

    GeoJSON Updates

    Corrects several instances of OL use to GeoJSON. WME-Utils/NavigationPoint.js still needs updated to handle GeoJSON for RPP creation to work.

    Merge pull request #17 from fuji2086/patch-1

    GeoJSON Updates

  • v2023.12.01.01 2023-12-01

    Update WMEPIE.js

  • v2023.11.15.01 2023-11-28 Imported from URL
  • v2023.08.25.02 2023-08-25

    Update WMEPIE.js

  • v2023.08.25.01 2023-08-25

    Update WMEPIE.js

  • v2023.08.23.01 2023-08-23

    Update WMEPIE.js

  • v2023.07.27.02 2023-07-27

    Update WMEPIE.js

    GLE fixed. Bump version # and change updateMessage.

  • v2023.07.27.01 2023-07-27

    Update WMEPIE.js

  • v2023.07.26.01 2023-07-26

    Update WMEPIE.js

  • v2023.07.18.01 2023-07-18

    Update WMEPIE.js

  • v2023.07.14.01 2023-07-14

    Update WMEPIE.js

  • v2023.07.10.01 2023-07-10

    Update WMEPIE.js

  • v2023.06.13.01 2023-06-13 Update WMEPIE.js
  • v2023.05.22.01 2023-05-22 bump version # for GLE update
  • v2023.05.18.01 2023-05-18 Update WMEPIE.js

显示所有脚本版本