Get a sneak peek at whats next for Permanent Hazards on our April 7th Office Hours!
Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.
Post by JustinS83
russblau wrote: Fri Aug 25, 2023 5:41 pm New bug in WME 2.180 -- select a place, click the address field to edit it, then click in the House Number field. The field will be underlined in blue, indicating that it is active for editing, for about one second -- then it will deactivate (lose input focus), and hitting a number key will not have any effect on the house number (although it may have side effects elsewhere). 

This only occurs with PIE enabled.
 

 
Disable "Move HN entry before street entry"
JustinS83  
Waze Global Champs
Waze Global Champs
Posts: 1463
Has thanked: 215 times
Been thanked: 2389 times
Send a message

Post by JustinS83
SunDevil2213 wrote: Sat Jan 27, 2024 7:17 pm
jm6087 wrote: Thu Nov 30, 2023 12:05 am
V_Dorb wrote: Wed Nov 29, 2023 9:30 pm I have a bug for 2023.11.15.01 update . It's impossible to select segments on the map.
 
 
 



 
Most likely it is not related to PIE, it is related to number of layers you have active. 
Go to your console (F11) and in the console field enter W.map.layers.length
What number do you get?


 
I have 72/81 layers right now. If I activate PIE (and thus remove my ability to select any segments) my layers jumps up to 84. I've learned to just live with out PIE, which is unfortunate, because I loved the functionality. Not being able to select any segments when it's active is a dealbreaker. And not being able to have any other scripts active at the same time, because PIE needs to take up 12 layers slots makes it pretty unusable.

 
Incorrect, PIE only creates 6 layers.
 
JustinS83  
Waze Global Champs
Waze Global Champs
Posts: 1463
Has thanked: 215 times
Been thanked: 2389 times
Send a message

Post by JustinS83
SunDevil2213 wrote: Sun Jan 28, 2024 9:40 pmActually, my original statement was completely correct. PIE was turned off - 72 layers. Enabled PIE and changed nothing else, refreshed - 84 layers. I said what the layers were without it and with it, all else remaining equal. Interpret it how you want. 
 

 
It isn't interpretation.  "because PIE needs to take up 12 layers slots".  It doesn't, it needs 6 layers based upon settings.

I just tested on my system. 
Without PIE: 54 layers
With PIE: 59 layers

It isn't a script issue, it's a your computer issue.
JustinS83  
Waze Global Champs
Waze Global Champs
Posts: 1463
Has thanked: 215 times
Been thanked: 2389 times
Send a message

Post by JustinS83
russblau wrote: Mon Jan 29, 2024 3:53 pm In WME Prod, when I create a new RPP using the keyboard shortcut, my PIE options are recognized (the place is locked to R2, the closest street name is auto-filled, etc.). However, when I create a new RPP from the Places menu instead, these options are not implemented (the place is locked to R1 and has no street name).
 

 
See here: viewtopic.php?p=2365224#p2365224

The Place menu is completely native due to recent(ish) WME changes.
JustinS83  
Waze Global Champs
Waze Global Champs
Posts: 1463
Has thanked: 215 times
Been thanked: 2389 times
Send a message

Post by JustinS83
russblau wrote: Mon Feb 26, 2024 7:00 pm Here are a few outstanding issues with PIE (all of them reasonably minor, but just listing them so they don't get overlooked) --
  • When creating a new RPP with the keyboard shortcut, the option 'When the primary is "No city" look for an alt city' is failing to work in some cases, although not consistently. On one occasion, the console showed the following error, although in other cases there was no error message:

Code: Select all

WazeWrapLib.js?_=1708972932868:612 Uncaught (in promise) TypeError: mygeometry.distanceTo is not a function
at Geometry.findClosestSegment (WazeWrapLib.js?_=1708972932868:612:52)
at findNearestSegment (userscript.html?name=WME-Place-Interface-Enhancements.user.js&id=a5521725-bb88-4960-b15f-b7aa86c4e48b:7144:44)
at userscript.html?name=WME-Place-Interface-Enhancements.user.js&id=a5521725-bb88-4960-b15f-b7aa86c4e48b:7180:29
So far, I can't tell what causes it to work sometimes and not others (except that it always seems to work OK when I am creating the RPP in Maryland, and not when it is in Virginia!).
  • The keyboard shortcuts for "Create item 1", "Create item 2", etc. don't work at all. I assume this probably has something to do with the change to the WME Place menus that you mentioned previously,
  • The "Clear Geometry" button doesn't seem to do anything. The following error message appears in the console when this button is clicked:

Code: Select all

Uncaught TypeError: Cannot read properties of null (reading 'getCenterLonLat')
at HTMLElement.<anonymous> (userscript.html?name=WME-Place-Interface-Enhancements.user.js&id=a5521725-bb88-4960-b15f-b7aa86c4e48b:7949:67)
at HTMLElement.dispatch (third_party-8087a682941f6d65.js.gz:2:2001950)
at g.handle (third_party-8087a682941f6d65.js.gz:2:1999941)
  • The "Show Place names" option is obsolete, since this capability is now native in WME, and could be removed.
Thanks, most of these are on my list.  Some of the issues are caused by the OL distanceTo calculation disappearing.
The "Show Place names" option is obsolete, since this capability is now native in WME, and could be removed.
Yeah, except I hate the native display.  It doesn't center properly over large areas, the font blends in with the map, and it only shows at zoom 18+.  It's a failed attempt at replicating my feature.
 
JustinS83  
Waze Global Champs
Waze Global Champs
Posts: 1463
Has thanked: 215 times
Been thanked: 2389 times
Send a message

Post by KillianDuSud
Hello, I've been using PIE for making a lot of POI, got a break for half a year and now, I lost a good feature I was always using. I'm talking about the auto-fill opening hours. The box disappeared from the menu for me.
Yet I've no idea how to change or fix a code  and wants to know if anyone else have this issue and if there's a possible fix for it.
 
image
KillianDuSud
Posts: 36
Has thanked: 11 times
Been thanked: 8 times
Send a message

Post by Kkervinjones
With the latest production of WME (and beta), with PIE (v2018.04.24.02) enabled, I seem to be having problems adding point places onto the map. Whenever I select a new point place menu option, the mouse cursor remains the same, without the 'point place' hovering with it (the hovering point seems to get stuck just under the menu in the grey bar).

If I click in the grey bar, when trying to add a new Point Place, the place is added, but the following console error shows:

Code: Select all

userscript.html?id=5…2-12aa2e9589de:5989 Uncaught TypeError: Cannot read property 'id' of undefined
    at createPlace (userscript.html?id=5…2-12aa2e9589de:5989)
    at endPlacementMode (userscript.html?id=5…2-12aa2e9589de:5928)
    at HTMLDivElement.eval (userscript.html?id=5…2-12aa2e9589de:5812)
    at HTMLDivElement.dispatch (vendor-c9d9d1a….js:24)
    at HTMLDivElement.p.handle (vendor-c9d9d1a….js:24)
createPlace	@	userscript.html?id=5…2-12aa2e9589de:5989
endPlacementMode	@	userscript.html?id=5…2-12aa2e9589de:5928
(anonymous)	@	userscript.html?id=5…2-12aa2e9589de:5812
dispatch	@	vendor-c9d9d1a….js:24
p.handle	@	vendor-c9d9d1a….js:24
If I switch PIE off, and refresh, I can add Point Places as normal.

I'm able to add Area Places ok. So obvious workaround is to add an area place and convert it to a point.

I've switched all other scripts and toolbox off, so there's no interference from anything else.
Kkervinjones  
Waze Global Champs
Waze Global Champs
Posts: 4055
Answers: 11
Has thanked: 1113 times
Been thanked: 1650 times
Send a message
Keith
UK Country Admin and Global Champ
Area Manager for North West England and the Isle of Man
Google Pixel 5 (Personal)/iPhone 8 (Work) - Carplay/AA - 2021 Toyota Corolla

https://s.waze.tools/gc.pnghttps://s.waze.tools/c6s.pnghttps://s.waze.tools/s0500.pnghttps://s.waze.tools/betc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/tem.png
https://i.imgur.com/nW244c6.png

Post by Kkervinjones
Anyone noticed that when you hover over a Gas/Petrol Station brand the external provider distance indicator is showing? I'm sure it didn't do this before.



No harm done, but it did confused me for a minute.
Kkervinjones  
Waze Global Champs
Waze Global Champs
Posts: 4055
Answers: 11
Has thanked: 1113 times
Been thanked: 1650 times
Send a message
Keith
UK Country Admin and Global Champ
Area Manager for North West England and the Isle of Man
Google Pixel 5 (Personal)/iPhone 8 (Work) - Carplay/AA - 2021 Toyota Corolla

https://s.waze.tools/gc.pnghttps://s.waze.tools/c6s.pnghttps://s.waze.tools/s0500.pnghttps://s.waze.tools/betc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/tem.png
https://i.imgur.com/nW244c6.png

Post by Kkervinjones
Ok, I think I found out more about the symptoms. It's only showing distances for the first few Gas Station brands, and it only does it after I've done a search for an external provider. The distances given are in the same order that they are in the external providers list, making me think the two are being linked together.

In the below examples, I'm hovering over the second option in the list - Shell Island which is 113mi away. I'm then hovering second option in the Brands list - ASDA, and it shows it's 113mi away.

I've only found this by accident. Not a major issue, but it did confuse me when I was looking at Brands.


Kkervinjones  
Waze Global Champs
Waze Global Champs
Posts: 4055
Answers: 11
Has thanked: 1113 times
Been thanked: 1650 times
Send a message
Keith
UK Country Admin and Global Champ
Area Manager for North West England and the Isle of Man
Google Pixel 5 (Personal)/iPhone 8 (Work) - Carplay/AA - 2021 Toyota Corolla

https://s.waze.tools/gc.pnghttps://s.waze.tools/c6s.pnghttps://s.waze.tools/s0500.pnghttps://s.waze.tools/betc.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/tem.png
https://i.imgur.com/nW244c6.png