1.34 adds "last comment less than x days" filtering

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

dknight212 wrote: Actually, the forum doesn't seem to want you to be thanked at all ...

So thank you thank you thank you!

Things got a.bit screwed up when my username was changed over to be wiki-compatible, lost all my thanks counts and special forum access rights, but my post count went up by several thousand... waiting to hear back from Waze support again to see if they can fix it all.

1.35 adds support for "Blocked road" URs...

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

shawndoc wrote:I often have problems with the URO script not loading. I often have to reload the editor several times before it shows up and starts doing its thing. Any suggestion on what could be causing it?

Since the recent integration of Google bits into WME, I've noticed that WME itself now takes longer to fully initialise (seems to be the call to https://www.googleapis.com/tile/v1/viewport that's slowing things down). As with most addon scripts, URO requires certain parts of WME to be loaded before it can complete its own initialisation, so any delay in WME completing its page load process will have a knock-on effect on how long it takes URO to appear.

There have been times when WME is taking so long to finish loading (but with no obvious indication that it's still waiting for stuff behind the scenes) that it gives the impression URO isn't going to start up - I haven't tested every single WME load attempt to make sure that URO would always load eventually (like you I get bored with waiting and just force a WME reload to try speeding things up), but on the times I have deliberately left it alone to finish by itself, it's always done what I expect it to do, just a hell of a lot slower than it used to do...

If the WME startup times don't improve in the near future, I'll look at changing the URO initialisation code so that it can start up as soon as all the necessary bits of WME are loaded, rather than simply waiting for *all* of WME to load.

Following a request from pvaladares to include regex support in LMUR for keyword filtering, it seemed sensible to add it to URO as well... It is not necessary to include the /.../ delimiters around the regex string - e.g. to find all URs that contain foo or bar in their descriptions, enter foo|bar (rather than /foo|bar/) into the appropriate keyword field.

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

Interesting info, thanks! Any other feedback like this from users who're able to consistently get URO startup failures would be most appreciated too - sometimes it's the smallest of clues that leads to a solution... Also useful to know which server you're using and whether it's the release or beta editor.

1.37 uses the native conversation markers in WME beta, inhibits the display of "null" comments in UR popups, and reduces the script startup time...

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

Partially correct - each UR object has a timestamp which is accurate enough to derive the date of submission (and hence the elapsed days since submission, as shown in the URO popups), but the accuracy of the time part is, deliberately or otherwise, degraded to the point where every UR timestamp decodes to a time of midnight...

shawndoc wrote:Any chance of my other request? Filtering by number of comments?

Technically possible yes, so I'll look into it this coming week.

I'll add that to the to-do list as well, thanks