3.13 includes the features requested by PesachZ, sketch and bz2012, namely:

• custom markers for URs tagged as [CONSTRUCTION], [CLOSURE] or [EVENT]
• infobox popup when a restricted segment is highlighted

Both these new features are optional and can be disabled via the Misc tab.

Note: the restrictions popup doesn't (yet) display any comments - given the size of the box I didn't want to make it any larger than it may already get on segments with multiple restrictions, so for now it just displays the essentials...


Firefox+Greasemonkey version: https://greasyfork.org/scripts/1952-uroverview-plus-uro
Chrome Web Store version: https://chrome.google.com/webstore/deta ... mjcdghdphi

PesachZ wrote:It may just be a publishing delay but the Google Chrome Webstore is still showing v3.12

I'd forgotten to hit the publish button and left 3.13 stuck in draft status... 3.13 is now available from CWS

3.14 now also provides the option to provide an info popup for landmarks/places, and fixes the problem where the segment popup would only update if the current segment was first unhighlighted before highlighting the next segment.


Firefox+Greasemonkey version: https://greasyfork.org/scripts/1952-uroverview-plus-uro
Chrome Web Store version: https://chrome.google.com/webstore/deta ... mjcdghdphi

3.15 is a compatibility update for the latest WME Beta release.

Firefox+Greasemonkey version: https://greasyfork.org/scripts/1952-uroverview-plus-uro
Chrome Web Store version: https://chrome.google.com/webstore/deta ... mjcdghdphi

3.16 introduces restriction comments to the popup as requested by bz2012, and green-hued custom icons for closed URs as requested by jasonroseweir (sorry I overlooked this at the time ) and ditchi56 (thanks for the reminder ).

It also fixes the Select Roundabout Segment functionality in WME Beta, and puts in place a few other behind the scenes changes to make better use of the native WME code both in beta and production versions of the editor.


Firefox+Greasemonkey version: https://greasyfork.org/scripts/1952-uroverview-plus-uro
Chrome Web Store version: https://chrome.google.com/webstore/deta ... mjcdghdphi

3.17 now embeds all the custom images witihn the script source, as opposed to the half-embedded, half-remotely-served-up approach used in previous releases. This resolves the server-inaccessibility issue which began earlier today causing the comment count and yellow/green comment circles not to be displayed.


Firefox+Greasemonkey version: https://greasyfork.org/scripts/1952-uroverview-plus-uro
Chrome Web Store version: https://chrome.google.com/webstore/deta ... mjcdghdphi

AlanOfTheBerg wrote:Has anyone officially requested Places category filtering from URO+ yet?

Showing/hiding the Place polygons based on their categories... I'll look into it. Thanks for the suggestion.

I'd be reluctant to over-simplify the keyword - as sketch suggests, [NOTE] would be fine because the chances of anyone entering that as part of a normal comment are pretty slim to non-existent, whereas your suggestion of using "WME" or "Editor" start to skate a bit too close to the "could reasonably be used in a normal comment" group of words we ought to avoid.


To be quite honest, anyone serious enough about editing to want to use these keywords whilst on the move really ought to be using a phone keyboard that allows for stuff like this to be inserted from a list of predefined text on entry of a shortcode.

On my Android phones I've been using the "Auto Text Keyboard Lite" app (formerly known as FireKeys Free) which lets me define 10 shortcuts, one of which is defined so that "lft" can be expanded to "Please leave for Twister-UK: " - this could just as easily be defined with "[NOTE] Please leave for Twister-UK: " as the expansion text, without requiring me to type anything extra each time I submit a report. AFAIK, similar functionality exists over in the iOS world.

3.18 introduces the following changes/updates:

• Added custom markers for [NOTE]-tagged URs.
• Re-opened map problems are now marked as such, and can be filtered.
• Places/landmarks/venues/whatever you call them can now be filtered by category.
• Events which occurred yesterday but less than 24 hours ago are now listed in their popup as having happened 1 day ago, rather than today...
• Optimised filtering code to minimise unnecessary operations.

The requests from bz2012 for popups on restricted turns and an open in new window link are being looked into, though at present I can't give any guarantees either of them will appear.


Firefox+Greasemonkey version: https://greasyfork.org/scripts/1952-uroverview-plus-uro
Chrome Web Store version: https://chrome.google.com/webstore/deta ... mjcdghdphi

Unable to replicate this in either FF or Chrome, and URO+ itself doesn't care about zoom levels anyway, it simply filters whatever data is presented to it by WME.

So if you're still not seeing older URs at wider zoom levels, it sounds as if your copy of WME isn't loading those older URs in the first place. What happens if you disable all extensions and reload WME - do the older URs appear then, or are they still missing until you start zooming in?