You will have trouble highlighting based on Auto-locks. The Validator functionality around this was built before auto-locks were introduced. I've tried many times, but Validator seems unable to distinguish properly between the actual lock level and the auto-lock level.

turbomkt wrote:

berestovskyy wrote:Thanks, yaacobyy. Will be fixed in the next release.

This should NOT be fixed. With two segments like the example, Waze may suggest a route via the wrong way. It's counter-intuitive, but I have seen it done. A two segment loop, even with one way segments, must be fixed.

I have to agree. In the app, routes are provided as a list of junction nodes. The app then routes from one node to the next. If there are 2 nodes with 2 separate segments joining the nodes, the app behaviour cannot be determined. The app may instruct the user to take one segment, but show the other segment being used on-screen. In URs, I have seen one segment highlighted as the given route with instruction icons for the other route.

Whilst it might seem obvious that Waze will not route the wrong way along a one-way segment, that is no guarantee of what instructions will be given, what the app will display or what will be recorded/reported in a UR. I think it's safer that we add the extra node - even if it seems intuitively unnecessary.

I don't think it's reported as a bug and would probably not be accepted anyway.

Waze routes node-to-node and always has done. We've been told not to map multiple single segments connecting a pair of nodes and that's the very reason checks like this exist. If we reported such a routing bug, I expect the reply would be "the map is incorrect and should be fixed".

Ideally, it would be nice if the app/routing engine could spot this problem. But it hasn't for many years and I don't expect it ever will.

theMadcabbie wrote:Feature Request

Is it possible to validate the correct abbreviations for Road names i.e Rd and St etc as per our UK list?

Thank you in advance.

The Validator Localization pack for United Kingdom already validates UK road names - although it hasn't been updated for names using the > symbol.

The update seems to have fixed multiple issues I was seeing:

• Alt-click on second segment not selecting all between first & second
• WME Toolbox failing during load 9 times out of 10 with missing highlights and an empty drop-down menu
• Attempts to set speed limits using WME Speedhelper behaving very strangely!

Thanks for the quick fix.

Brand new installation of this script, and it's not working as described in the last few posts. Installed fine, and to get it to display in the left panel also had to install WME Fix Map Object as described.

Click play, and it tells me "starting! layers are off to scan faster", and then nothing. It doesn't strictly crash, as I can still click around, and pause/stop, but no report appears and nothing else happens.

I've disabled all other scripts to troubleshoot, and this doesn't help.

WaseYves wrote:I got that message

WME Validator v1.0.2 error:
This build of WME Validator has expired. Please upgrade!

Try to re-install from Chrome Web Store.
Don't work.

How do i fix that ?

Same here. I installed it yesterday, so I have been able to use it for a couple of hours only.

I found the update: https://greasyfork.org/scripts/3895-wme ... ration-fix

Being a software developer, I find it extremely frustrating when code is obfuscated and its license prevents you from trying to figure out what it does. Especially so in a community setting such as Waze.

Luckily, Javascript itself is incredibly malleable, so instead of modifying the script, let's modify a part of Javascript that the script relies on instead ... at least in Firefox, adding this peace of code directly under the LICENSE comment in the Greasemonkey script makes the script work again:
Mind you, this may break all kinds of things, but as an emergency procedure while we wait for a new update, it works.

So, technically we're breaching the license, as it says "You may not modify [...] the script", although it could also be argued that we've modified a part separate from what actually constitutes the script part...

And, come on. If you're going to write code that expires, at least update it a while before it does. Even if the update consists of nothing more than extending the expiration date. In the next update, if the author wants this kind of behavior in place, they should add another check first that sends a request to see if there is an actual update ready before telling people the script has expired.