Lately all segment with phantom nodes are marked as simplifiable segment? I assume that's a bug?

https://waze.com/nl/editor?env=row&lat= ... =353323827

Hi,
not sure if it's a known issue, but the highlighting of simplifiable Segments didn't work.
I use Chrome 88.0.4324.150 and ToolBox Version 1.9.6.

Teststreet has much unneeded nodes.
Screenshot

Checked with all other scripts deactivated and only the TB option for that as active. You see it's not highlighting.
Screenshot

When you mark the segment, the simplify button is active and the segment can be simplified.
Screenshot

It's reproducable.

Regards
Peter

There are linked Screenshots in my initial post viewtopic.php?f=819&t=311973&view=unread#p2118376

I deleted my old teststreet because error is reproducable for me, now added a new one.
Permalink to test street: https://www.waze.com/de/editor/?env=row ... =401069139

For my tests (also for screenshots named above) are all tampermonkey scripts deactivated.
Other active Chrome extensions for Waze:

• WME Geometries
• Map Overlays

Additonal to my screenshots above, here my console output after an F5 of WME. Segment is not highlighting.
https://www.peter-online-gallery.de/waz ... 022021.png

WME Server: ROW

Hello,
I have tried to remove the revcons here, with the "auto fix" for revcons. (Have done two or three auto fixes before, that worked fine)

By doing this is got the following error message in the console:
app-dec6049c1541310903fa.js.gz:1 Uncaught TypeError: Cannot read properties of null (reading 'getNode')
    at e.value (app-dec6049c1541310903fa.js.gz:1:1009080)
    at e.value (app-dec6049c1541310903fa.js.gz:1:1008815)
    at e.value (app-dec6049c1541310903fa.js.gz:1:984683)
    at e.value (app-dec6049c1541310903fa.js.gz:1:984535)
    at v (third_party-60cee3a00789a7d46f06.js.gz:2:728838)
    at y (third_party-60cee3a00789a7d46f06.js.gz:2:728686)
    at d (third_party-60cee3a00789a7d46f06.js.gz:2:726639)
    at e.c.trigger (third_party-60cee3a00789a7d46f06.js.gz:2:728579)
    at e.value (app-dec6049c1541310903fa.js.gz:1:945673)
    at initialize.triggerEvent (third_party-60cee3a00789a7d46f06.js.gz:2:1771442)

and the save button is not clickable, there is an empty "action" in the history. (see screenshot)  
It not happend every time by "auto fix" revcons. After a reload it works also at this junction, but haven't done it here in case you would like to test.


Using Chrome 98.0.4758.102 and Toolbox 1.9.16
Regards
Peter
 
 

G_W1Z wrote: ↑Sat Jun 19, 2021 6:41 pm Feature suggestion: the ability to change the order of the features in the TB toolbar. Example: move to the end of the list the broom (suppress unneeded junctions) while allowing others typically behind it to show in front of it.

 

Was just thinking the same yesterday, the ones I frequently use are not in any reasonable order. So +1

SuperDave1426 wrote: ↑Sat Jun 26, 2021 12:28 pm

lg1992 wrote: ↑Fri Jun 25, 2021 3:09 am May I ask what's TIO?
 

Turn Instruction Override.
 

Just a sidenote: In my opinion the Glossary should should also be mentioned in answers to these questions for it to reach better visibility to users, even I have to visit it from time to time since we don't use same abbreviations in all local communities. https://wazeopedia.waze.com/wiki/USA/Glossary
 
 
 
 

Toolbox 1.9.17 not working on chrome 108.0.5359.125

Antes eu conseguir selecionar apenas os segmentos recém criados (não nomeados) pela toolbox, para assim poder nomeá-los. Agora ela não separa mais os criados por mim já nomeados dos sem nome. Alguém mais com esse problema?

Before I was able to select only the newly created (unnamed) segments by the toolbox, so I could name them. Now it no longer separates those created by me already named from those without a name. Anyone else with this problem?  


 

Hi guys, there is an issue with  new WME 2.92-9, it's reported here viewtopic.php?p=2215750#p2215750
The dropdown menu for speed cameras and "excess speed" field overlap each other with TB on.
Thank you!