I suspect the script doesn't highlight segments below primary streets if the zoom in the URL is 0-4 (it doesn't matter what is the real current zoom level). To override this bug you can click the chain icon in the bottom bar to match zoom in the URL to the current zoom level.phuz wrote:I have the script failing to highlight any PLRs.
Leonid, Country Manager, Israel
The script doesn't check for the current zoom level, but for the original one defined in the URL. As a result, if I open the editor with zoom level 2 or 3 and then zoom in, the script only marks primary streets ad higher types as locked.
To fix the problem it's enough to replace in 2 places W.map.zoom with W.map.getZoom()
To fix the problem it's enough to replace in 2 places W.map.zoom with W.map.getZoom()
Leonid, Country Manager, Israel
It's confusing that colors by a selected city differ for roads and places. I would prefer to see places pink too.
Leonid, Country Manager, Israel
Please add one more option to "Filter by City" - to mark segments and places with undefined city name if they are present on the map.
Leonid, Country Manager, Israel
Looks like version 2.180 has wrecked the script. Is it still actively supported?
With only this script enabled the filter by city isn't working. It happens when I try to open the selectbox for the cities.
Code: Select all
Uncaught TypeError: Cannot read properties of null (reading 'attributes')
at HTMLSelectElement.updateCityList (userscript.html?name=WME-Color-Highlights.user.js&id=e80113cf-653e-46bf-94f9-6b4d359102ea:998:49)
Line 152:
Code: Select all
var cityID = street?.attributes.cityID;
Code: Select all
var selectedCityMatch = (specificCity && venueStreet.attributes.cityID == selectedCityId);
(around line 990):
Code: Select all
for (var [cityId, city] of Object.entries(W.model.cities.objects)) {
cityIds.push(cityId);
cityObjs.push({
id: city.attributes.id,
name: city.attributes.name,
state: city.attributes.stateID,
country: city.attributes.countryID
});
}
Last edited by LihtsaltMats on Wed Aug 23, 2023 12:36 pm, edited 1 time in total.
While the script is being updated you can temporarily fix it by changing line 155:VILLAformer wrote: ↑Wed Aug 23, 2023 10:33 am Since yesterday, the "No Name (Orange)" option does not work for me. I have tried to reinstall the script and leave him alone active but nothing.
Code: Select all
var noName = street?.attributes.isEmpty;
LihtsaltMats wrote: ↑Tue Aug 22, 2023 3:10 pm In addition to the previously mentioned username changes. Maybe this will give you a little headstart:
Line 152:Line 663:Code: Select all
var cityID = street?.attributes.cityID;
Code: Select all
var selectedCityMatch = (specificCity && venueStreet.attributes.cityID == selectedCityId);
(around line 990):Code: Select all
for (var [cityId, city] of Object.entries(W.model.cities.objects)) { cityIds.push(cityId); cityObjs.push({ id: city.attributes.id, name: city.attributes.name, state: city.attributes.stateID, country: city.attributes.countryID }); }
These should fix that.
I hope the creator doesn't mind me sharing. It's just a very useful script.
An interesting suggestion to be implemented on this script is this one by @LostInMyMaps
We already have the advanced possibility to highlight (filter) by editor ... The possibility to filter by a specific level of editor (or multiple levels) would be a nice option
Thanks in advance
... that he made here .
- A layer that highlights segments/places touched by new editors/L1
We already have the advanced possibility to highlight (filter) by editor ... The possibility to filter by a specific level of editor (or multiple levels) would be a nice option
Thanks in advance
https://storage.googleapis.com/wazeoped ... nature.pnghttps://storage.googleapis.com/wazeoped ... itor_5.pnghttps://storage.googleapis.com/wazeoped ... anager.pnghttps://storage.googleapis.com/wazeoped ... anager.pnghttps://storage.googleapis.com/wazeoped ... lizers.pnghttps://storage.googleapis.com/wazeoped ... tester.pnghttps://storage.googleapis.com/wazeoped ... er_new.pnghttps://storage.googleapis.com/wazeoped ... aiders.pnghttps://storage.googleapis.com/wazeoped ... s_300k.pnghttps://storage.googleapis.com/wazeoped ... s_100p.pnghttps://storage.googleapis.com/wazeoped ... _65px1.pnghttps://storage.googleapis.com/wazeoped ... 2/Gnat.gif
PORTUGAL
PORTUGAL
Thank goodness I am not the only one. I didn't realize Chrome updated but in the last 48-72 hours, the Highlights stopped working on my machine too. Found the 1.6.4 link and am back in business. Thanks again!
[img]https:///WS6zp[/img][img]https:///0NAfp[/img]
Re: [Script] WME Color Highlights - 2.28 July 2019