3.1 should fix the blank tab panel problem mentioned by far too many people above The problem was introduced with the inclusion of the DTE functionality, but only becomes apparent if URO+ performs the DTE-related part of its startup sequence after WME has finished playing around with the panel. In this hidden state, doing anything in WME that causes it to redraw the panel (e.g. selecting a segment) then restores visibility for the remainder of the session.

I've also fixed the settings backup feature so that it uses the current setting values from the UI, rather than the values that were saved during the previous script shutdown.


Edited to add: Both Greasemonkey and crx versions are now up to date...

Firefox+Greasemonkey version: http://userscripts.org/scripts/show/145186
Chrome packaged version: http://crx.chizzum.com/UROverview.crx

I don't plan on pulling the existing versions from userscripts or my own server, but neither do I plan on doing anything more with them (or sticking them on CWS in the case of the Chrome versions), so the standalone versions will still be useable until Waze decide to mess around with WME again...

*sigh* it never ceases to amaze me just how many different ways the Waze coding team manage to find to implement the same outward functionality with every WME refresh... I've just had a similar bug report from another user, so I'll look into it when I get some free time - probably next week at the earliest.

3.2 restores WME beta compatibility...

Firefox+Greasemonkey version: http://userscripts.org/scripts/show/145186
Chrome packaged version: http://crx.chizzum.com/UROverview.crx

CBenson wrote:Is there a way to show only URs where the Reporter is the last commenter?

Yes

Version 3.3 revises the comments-related UR filter options, the correct combination of which now allows only URs where the last comment was made by the reporter to be shown, as requested above...

3.3 also marks the debut of URO on the Chrome Web Store. Users of the older CRX-packaged versions should uninstall them first before installing 3.3 from CWS.

Firefox+Greasemonkey version: http://userscripts.org/scripts/show/145186
Chrome Web Store version: https://chrome.google.com/webstore/deta ... mjcdghdphi

Firefox or Chrome?
Userscripts or Chrome Web Store version?
Production or Beta WME?
Which other scripts are installed?

You've got both URO+ *and* URO installed?

qwaletee wrote:URO+ 3.3 and LMUR 2.4. The latter operates on Livemap, not WME, or at least is advertised as such.

I'm pretty familiar with the scope of LMUR's operations (I did write it, after all ) so yes, I can confirm that LMUR has no effect in WME. My query was more to do with your listing URO in response to me asking which *other* scripts you had installed - I wasn't sure if this meant you had both URO and URO+ installed, or if you'd just listed *all* the scripts...

Since I need to do a new release of URO to fix whatever Waze have done to break it in the latest beta release, I'll take the opportunity to both ponder the code relating to UR popup generation in case there's something obvious which might be causing the problem, and to add in some extra diagnostics output to the debug console - if I don't find anything to change in the popup code, at least the next release will give me some more clues as to why it's behaving the way it is on your system.

As mentioned in the reply above, I'm aware of an issue with URO+ 3.3 and the latest WME beta release which is preventing UR popups from appearing at all (rather ironic given the problem qwaletee is having...), so I'll be looking into that soon - if anyone spots any other beta-related issues please let me know ASAP.