Recently when editing in Russia MapRaid area, I am extensively relying on the "Show alternative names" box to see the alternate names highlights. The problem is that they are not highlighted if the roads are not editable to me. This is a huge issue because I want to be able to see all attributes, highlights, and "TODO" from Magic on all segments, even outside my editable area. It is especially important for finding issues on roads locked higher than my rank. In fact, it is misleading to say that "Show alternative names" will be highlighted when it actually does not highlight. I thought something was broken, yet this is controlled by the configuration. Please give thanks to this post if you support this idea. Thanks!

The url used by WME Magic Changed a while ago since dbcm change his servers.

Dbcm releases many versions and does not tell us change log for EVERY release of WMEMagic. Most likely implementation of very small code changes / tweaks

Would it be possible to let Magic check for nodes on a tile border like these:


 
These generate problems in the app with routing. It makes the car spin.
There is a bugreport on CC with more examples.

I allready tried contacting you by email, but as you have a dedicated forum topic of this script, I'll ask my question here

My request is, to have the glow on the segments stand out a little bit more. Especially with new segments, the faded blueish color is very hard to distinguish.

Great script though!

Is see several instances of "Geometry nodes too close" in the editor, but I cannot see any problem with the indicated segments. So, I wonder what causes these marks, and if I am just missing something.

For example, I am seeing this:

https://www.screencast.com/t/zG5lHsO4GY

For this screenshot, I have turned on most map features.

Here is a permalink to the map:

https://www.waze.com/en-US/editor?env=u ... 19&zoom=10

FWIW I am a newbie at this. I appreciate any help you can give me.

Thanks!

jm6087 wrote:Drag this node around and you will see the "overlapping"
https://www.waze.com/en-US/editor?env=u ... =510365074

Perfect! Thanks for the lesson.

Would it be possible to add the header below in the meta header? I can understand wanting to host the script on a server you manage yourself instead of GreasyFork, but as it is people don't get any updates when they use GreaseMonkey. With just this addition the extension will know where to search for updates. This is also useful for TamperMonkey as any script that was copy-pasted into TamperMonkey instead of added by opening the file in the browser currently doesn't get any updates either.

Hey, please be aware your script still seems to rely on the Waze object, which will be removed in one of the upcoming beta releases. You can test this yourself in the beta environment as the proxy object implemented by Waze (to make window.Waze point to window.W) also logs an error in the web console now.

It might also be that you've implemented code that checks whether the window.Waze object is missing, which would make this a bit of a false positive. But there's currently no reason to still check for it as the window.W object is present in both environments now.

Warning, this script no longer works in production due to W.location having been removed! You can find more information on what was changed and how to handle it in that topic.