SuperDave: I’m pretty sure that was already noted – the feature was removed when the beta went live because it was a fundamental change.
Unfortunately, given that Timbones is based in the UK, I suspect we’re still a while before the new system is implemented – “Places” only went live on the NA server. The ROW and IL servers are still a few weeks away, apparently.
I hope Tim will choose to reimplement that feature – I really liked it, especially for finding smudges being caused by landmarks. We will have to see, though!
That’s an extra step for someone to remember during scanning. And one that most editors won’t do – Shift-Z mode is great when I remember to do it, but most of the stuff I find with WMECH and Validator are incidental to editing things nearby to the issues they highlight for me. Normal editing has Shift-Z off.
It is not advisable (nor prudent) for an editor to be using extensions until they’ve mastered the base editor.
I don’t think this should be highlighted. There’s been argument about not highlighting uturns, even – that didn’t get removed from WMECH, but there wasn’t an easy way to notice them.
I think there are more important things to be highlighted – I’ve modified my WMECH to highlight streetnames that don’t conform to abbreviation standards, highlight end-point junctions that have u-turns or soft turns set. That said, I’m not publishing these changes – if Tim wants to include them, I’ll share the code, but they’re features that help my editing, but I don’t think they should be made available.
This fits in that category, too. If you feel you need it: fine. I trust you’re actually watching what you enable.
The biggest issue I have with this is that there are probably as many intersections that have restrictions as those that don’t. I don’t want to see something highlighted that is probably correct.
If you wanted to get fancy and could somehow highlight it when disabled straight-through and right-turn connections are highlighted (but not when a left-turn connection is the only one disabled), then that would be useful and probably worth integrating.
Has Waze broken this script again? I’m going on three days with it not loading. I even deleted and reinstalled it from the chrome store with no luck. Other scripts are working fine.
It’s working fine for me. Try disabling all your other scripts and see if the Highlighter works for you then. If it does, you’ve got a conflict with another script. To find which one, start re-enabling them one at a time until you find the one that’s causing the conflict.
I think the version is 35,but I’m not at home to check for sure.
Chrome started saying last week that I would not be getting any more updates because Google is no longer supporting my hardware. They’re dropping support for processors that don’t have sse2 or better, but I don’t see why that would affect any scripts.
Disabling and re enabling the color highlighter script fixed my problem, but now the WME toolbox one won’t come back! D’oh.
I really don’t see a big need for this new feature indicating levels. Other than railroads, and the occasional overpass that is set to the wrong level, what is it’s use? This would/will be kept turned off as I want to see lock level issues and other real problems on the roads that most commonly need to use elevations (freeways), not levels. Levels only really affect how the map is drawn, two segments can cross at the same level, abd two segments at widely carried levels can be connected and neither situation will effect the routing.
