[Script] WME Color Highlights - 2.38 Jan 2024

Just noticed something different.

I always have selected Recently Edited and Filter by Editor
I use to show both, now it seems to add them as a filter to each other.
If that was the original way it was to work, then can we have the option to split them again.
I can see the use for both options.

Thanks Always for this great tool. JD

It looks like today’s WME update has broken WME Color Highlights. More specifically, Highlighting unpaved no longer works.

I see that WME Color Highlights works properly in WME Prod, but not in Beta. Marking locked roads doesn’t work. Marking objects belonging to a city marks places but not roads.

Not working in beta, yes :frowning:

The v2.24 it’s working here

Hello and excuse me…, can you insert highlight segments that have:
manual lock equal to or less than the automatic lock
or lock less than or equal to a certain value?

There is no similar combination in any other tool but, at least for me, it would be very important to have an adequate level of lock in my area.

Would not it be useful for you too?

Both of these features are available to some extent in Toolbox.

Toolbox has a segment highlight that shows segments manually locked below, at, or above their auto level: red for segments manually below auto, green for segments manually above auto, cyan for segments at auto but manually locked.

You can also use the Toolbox Select Segments tool to select segments with a particular value.

You’re right.
I would explain what I mean because that feautures are present in Toolbox but not in combination.
Informatically I mean:
(manual lock <= automatic lock) OR (lock <= lock value).

This could highlight also segments at lock level 1 with automatic lock 1.
In toolbox hasn’t this combination.

Can we have a new highlight for Next to carpool/HOV/bus lane, recently stumbled across a random segment marked with this attribute. Guess it doesn’t really harm anything when a segments as this marked with no HOV lane nearby…

I just installed WME Color Highlights, but it’s not working. Is there anyone who is facing the same problem? Any idea how to fix this?

Using v2.24 from here?

I installed the extension using the link to the chrome store that is available in the first page of this topic.

Anyway, I tried to install the extension using the link you send, but it didn’t work. After the installation was finished, I couldn’t activate it.

The following message was shown: “this extension may have been corrupted”.

I would uninstall the extension you installed from the first post, v2.23 doesn’t work right. The one I linked (v2.24) is a script, not an extension, and it does work.

Sorry, that was my fault. It’s working now.

Thank you!

1 Like

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.

Thanks for the reminder. I’ve just pushed an update for WME Colour Highlights for this.

v2.25, available now from Greasyfork and Chome Web Store:

  • Localised road types!
  • Added Narrow Streets (or whatever it’s called in your language)
  • Auto-enable checkbox when selecting from drop-down

Enjoy! :ugeek:

1 Like

I met several problems with the version 2.25.

On the beta WME the add-on doesn’t appear at all. Details of the extension show that it has permissions to read and change data on editor-beta.waze.com and www.waze.com. But the URL of WME beta is beta.waze.com!

On the regular WME, when I select a city in the “Filter by city” combo box, the check box is indeed selected by itself, but only segments belonging to the chosen city are marked yellow. Places aren’t marked. I have to unselect and select again the check box to see also the places marked yellow. Then, if I select another city in the combo box, new segments become yellow, but the places belonging the first place still remain yellow.

I just came here searching for this same issue on Beta. Works fine in released WME.

I think that // @include /^https:\/\/(www|beta)\.waze\.com\/(?!user\/)(.{2,6}\/)?editor\/?.*$/ is what is generally being used now.

Thanks for this - I’ve fixed both these issues in version 2.26 (plus some other improvements).

1 Like