Twister-UK wrote:This is related to a bug in WME which is causing it to forget the data associated with segments after certain operations - if you've got segment popups enabled and they start showing "non-existent streetID" instead of the actual segment name, or if you click on a segment and it shows "No address" in the left-hand side panel instead of the actual name, then it indicates WME has lost the data.

At this point, any closures added to segments will be generated with blank location data - WME knows which *segment* the closures are being added to, but not which *streets* those segments relate to. Unfortunately, blank location data is also a trait of closures generated from the Waze app and, until this WME bug surfaced, was the only way to differentiate an in-app closure from a WME one...

Waze staff have now informed us that this bug has been fixed, though at present there's no indication when this fix will turn up in the production version of WME, so until this happens please be patient and pay attention to any unexpected loss of street names.

I still have this BUG in the latest beta WME.Is there a separate BUG report about this issue?

would i be possible to have a setting to turn of the app created closure highlighting. it's getting kind of tedious to edit closures i have made because they are flagged by URO+. thank you for your consideration.

In 3.168, unticking the master enable checkbox (to the right of the script version number at the top of the URO tab) now adds in-app closure highlighting to the list of stuff that gets switched on/off without the need to disable the entire script via the Tampermonkey menu...

ojlaw wrote:would i be possible to have a setting to turn of the app created closure highlighting. it's getting kind of tedious to edit closures i have made because they are flagged by URO+. thank you for your consideration.

As the incorrect classification of in-app closures is being caused by a WME bug, I'd prefer not to add a specific setting just to disable this, so I hope including it as part of the script which is now controlled by the master enable checkbox will suffice.

Hmm, interesting point. The introduction of the car/bike/taxi icons was intended to provide an at a glance indication as to whether or not each of those supported vehicle types would be affected by the restriction, regardless of how the restriction was actually set up (i.e. as a "vehicle types permitted" vs "vehicle types prohibited") one.

From my perspective, when dealing with routing issue reports where a malformed restriction might be responsible, all I care about initially is whether or not someone running the Waze app with their vehicle type set to one of those three options would or wouldn't be affected by the restriction, so the popup info was tailored to give me the instant summary I'd need to decide whether or not to then dig further into the restriction details via the native view/edit UI.

The only thing this icon-based overview fails to do (mainly because I keep forgetting the feature exists in WME at all) is indicate toll-based restrictions. I also note that URO doesn't even indicate when a segment has the global toll attribute set, even though I thought I'd added that in a while ago... So I'll certainly add toll support to my to do list here, though unless I can think of (or someone can give me) a compelling reason to do it another way then I'll likely just add it in as part of the icon-based overview rather than listing toll/toll-free restrictions seperately.

UR/MP centre-on-click inhibiting is now done in a way which doesn't rely on WME itself inhibiting auto-centre if marker attributes are adjusted, and both types of inhibit are now user-selectable in the Misc options tab