3.115 fixes the multi-part PUR problem noted by lg1992, lists TBR restricted vehicles by name instead of number in the enhanced history (as requested by atrophicshiner), and also now lists all vehicle types associated with a given TBR restriction instead of only the first type listed in the restriction data...


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

3.116...

...restores correct operation of the Next->Done button replacement feature if both UR and MP replacement options are selected.

...constrains the height of the alert box if its contents would otherwise cause the top and bottom of the box to be pushed out of the visible area.

...adds an "Accept all changes" button to the OWL tab - this allows all changes to watched cameras to be updated in the watchlist with a single click, instead of needing to visit each camera in turn and select the "Upate watchlist entry" from its popup.

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

Not a bad idea, I'll have a think about getting that into the next release... In the meantime, do remember that each type of popup can be individually inhibited via the controls on the Misc tab, and popups can be temporarily closed by double-clicking them without the need to de-highlight the associated map object.

3.117...

...restores compatibility with the new-look WME Production UI

...renders all users names inserted into the UI by URO+ as links to the relevant editor profile pages

...adds option (lurking on the Misc tab) to move the "AM's responsible for the point on the map directly under the mouse pointer" list from the bottom of the URO+ sidepanel tab into the existing WME topbar, replacing the existing and somewhat less than useful "AM's whos IDs happen to exist in the underlying map data model, even if they aren't responsible for *any* part of the map currently visible in WME" list that WME may or may not choose to render itself. To improve legibility of the AM list when rendered in the topbar, the background colour of the bar is also changed to solid black.

Note that changes to this option only take effect on the next WME session reload.

...automatically suppresses popups for area map comments if any other object is highlighted whilst the mouse pointer remains within the boundary of the comment area. Moving the pointer out of and back into the comment area will allow the comment popup to be shown again.


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

juliansean wrote:

Twister-UK wrote:3.117...

...restores compatibility with the new-look WME Production UI


...automatically suppresses popups for area map comments if any other object is highlighted whilst the mouse pointer remains within the boundary of the comment area. Moving the pointer out of and back into the comment area will allow the comment popup to be shown again.

Thank you for all the fixes and updates, but specifically for those two!

Thank Iain for the suggestion which got me thinking about the latter...

Ooh, good catch! I've now fixed this internally, so I'll push out an update hopefully tonight.

3.118 fixes a couple of small compatibility issues with the new look WME UI.


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

3.119 restores its tab after switching between WME measurement units (thanks to BellHouse), and adds speed limit filters for red light cameras.


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

Hmm, interesting... I've never noticed that before myself, and it's certainly not intentional, but given the way unstacking works (and if anyone knows how it does, please let me know ) it doesn't come as much of a surprise to learn that the one relies on the other.

I'll look into fixing this so...metime in the near future

RussPA wrote:This looks like debug info, but my console has thousands of these lines

It's a combination of a recent change in how URO maintains its knowledge of where to locate the map layers it needs to interact with, plus a minor error in the last release version where I forgot to change the default debug output setting back from its development state to the release state.

I'll correct this in the next release. Until then you can toggle the setting on a per-session basis by going to the URO+ tab and clicking on the version number to show or hide the (dbg) suffix. Just remember that each time you reload the WME session with 3.119, the debug output will be re-enabled.