Even switching between US and UK English, I still can't reproduce the error here. If you've got any other scripts running, please check with those disabled, as I think I know a route by which the error *could* occur, but I can't see any way for it to get into that state without the "assistance" of another script making changes to WME...

3.103 adds the following features:

• Places can now be filtered if they do/don't have any description text
• Place description text shown in place popup
• Segment lock level shown in segment popup
• RTC markers can be hidden based on their origin - WME or app

The lock level is shown either in the format "Lock: Ax" if the segment only has an auto lock level set, or in the format "Lock: Mx / Ay" if the segment has been manually locked.

The RTC marker filtering controls are currently lurking on the Misc tab. I have a few more ideas for RTC filtering options, and so if they come to fruition I'll probably add a RTC tab to house all the controls.


And no, to those with an interest in this particular topic, I still haven't forgotten about adding some sort of custom markers for map comments, but it's still not done yet...


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

I'll have a look into it, about time I re-enabled full support for this kind of PUR - note that they don't generate pop ups either...

3.104 adds the following features/fixes:

• Popups and auto-centre blocking now works for (P)PURs again
• TBR details are now shown in the popup for all turns, not just those going from an A-B to a B-A segment...
• Feed filter settings are now saved/restored
• Visible feed entries can be deleted, with optional auto-reload/delete

Whilst I'm aware of the Clear Feed script, that was designed around the very specific purpose of clearing *every* entry from your feed. The URO+ implementation of feed entry deleting can be used in the same way as Clear Feed if that's what you desire - simply deselect all feed filtering options, select the auto-refresh option next to the "Delete visible feed entries" button, then click the button and wait...

The clue to the difference in implementation comes from the button text - unlike Clear Feed, URO+ will only delete feed entries which are visible after taking the feed filter settings into account. So if you aren't interested in certain types of feed entry (e.g. place updates, entries from a country you've recently visited on holiday where you used Waze but have no intention of editing etc.), then simply set up the feed filter settings to show only those entries, and then let the delete process do its thing. Once it's finished, clearing the filter settings will then allow all the feed entries you *are* interested in to appear again.


To avoid any clashes if a user already has Clear Feed installed, this functionality is turned off by default. To turn it on (after uninstalling Clear Feed if necessary), go to the URO+ Misc tab and tick the "Enable delete feed entries button" checkbox.

If the auto-refresh checkbox next to the delete button is ticked, URO+ will refresh the feed list and continue deleting any newly loaded and unfiltered entries it finds, until the server stops providing any new entries which would be left unfiltered. As this can take some time to complete, unticking the box will also stop the delete process after the next refresh cycle.

Note also that due to the way feed entries are returned from the server, it cannot be guaranteed that all available feed entries will be deleted when using a set of filtering options which might require several feed reloads in order to find the next new unfiltered entry.

One limitation compared with Clear Feed is that, by not deleting every feed entry (unless that's how you've configured your filter settings), the feed list will start to fill up with hidden entries which may cause some drop in performance as WME tries to maintain the feed list. Reloading the WME session will resolve this, but URO+ will not attempt to do this - it's up to you to decide if and when this is necessary.


And no, to those with an interest in this particular topic, I still haven't forgotten about adding some sort of custom markers for map comments, but it's still not done yet...


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

Ah crap... One of the undocumented changes in 104 was to replace the last handful of calls to the native browser alert() function with calls to the custom alert requester within URO itself, and it appears this has now blocked the Done button handler from running correctly if no alert requester is required - i.e. every time you click Done *except* for when you've forgotten to send your latest UR comment.

I'll push out a fix for this at some point tonight.

3.105 fixes the breakages recently introduced along with the PPUR support...


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

3.106 correctly handles reloading of the feed filter keyword setting...

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

3.107 sees the introduction of enhanced segment edit history entries...

Specifically, when you now view certain types of entry within the segment edit history list, you'll see slightly more information than WME normally provides. Edits to turn restrictions now provide sufficient detail to identify the specific turn restriction being referred to, and edits to RTCs now show the details of the RTC - start/end times, description etc. - where these are available.

As this is still a bit of a work in progress feature, it's possible that it doesn't work correctly on some segments. If it appears to be misbehaving, please send me a permalink to the segment in question so I can investigate further.


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

These suggestions are now work-in-progress...

Olestas wrote:Drive Tab Enhancement (DTE) DOes not work anymore for me

Thanks, it's now working again in the development build.