voludu2 wrote:I see this with yellow arrows, as well -- I cannot edit the time based turn restriction because the pop-up covers the clock face.

You'll be pleased to hear that 3.54 also fixes this problem...


...by completely breaking the TBR popup functionality (note to self, undefined == null, but undefined !== null) I've fixed this for the next release and will also look at adjusting the popup position based on the location of the clockface rather than its parent arrow.

3.55 brings the following changes:

• TBR popups work again.
• TBR editing UI can be opened from within the TBR popup.
• Tweaked positioning code for all popup types.
• Restoring saved settings works properly if the current camera watchlist isn't empty but the restored settings contains an empty list.
• Various performance optimisations.

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

Not sure how this bug got past pre-release testing given how many custom tagged URs I've got in the areas I use for debugging, but I'll be releasing a fix for it later today... Apologies for any disruption it's caused.

rccoros wrote:Anyone else experiencing the issue on the check box for "Last comment less than x days" not working?
This has been working previously for me but now only the "Last comment more than x days" works.

Doh... a fix for this is also in place for the release later today

If you enable debug output (click on the version number in the URO+ tab), do you see anything in the debug console when this rogue popup reappears?

Unable to replicate this in Chrome or Firefox... Does the save icon activate when you click the Solved or Not Identified radio button and then deactivate again when you click Done, or does it remain deactivated throughout? I also see you're running some other add-ons - does the problem still exist if you deactivate all of those and leave only URO+ running?

3.56 restores correct behaviour of custom UR marker/comment count/etc and the comment age filters... Note that due to some last minute hitches in fully resolving the former, I completely forgot that I'd resolved the latter earlier today, hence the lack of any reference to it in either the GreasyFork release notes or the "what's new" popup within URO+ itself.


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

3.57 is mostly a bunch of fixes for WME Beta users. For non-beta users, the only change is that URO+ now doesn't even attempt to run in practice mode, as opposed to doing it's best but not really working quite the same as when you're logged in. In all honesty, the only reason I ever tried getting it working in practice mode was to let me do some debugging of stuff on the US server in the days before I got an AM area set up over there, and with all the headaches of trying to keep on top of the changes in the beta I just don't have the time to expend on attempting to maintain practice mode semi-compatibility, so the only sane option was to kill it entirely. If anyone is *really* inconvenienced by this change, please get in touch...

Anyhoo, back to the changes for beta users. The big change is that it now works again, at least on my FF and Chrome setups. Feedback would be welcomed from any beta users who saw problems with previous versions, particularly Chrome users who seemed to be hit hardest.

Additionally, there's now an option in the Misc tab to hide the stupidly large user info section at the top of the sidebar, and the links in the menubar at the top of the screen (livemap, support etc.) are now rewritten to point to http://www.waze.com instead of being relative links which have never, ever, worked on the beta server...


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

Aww crap, that's what happens when you accidentally package an older version of the manifest file... Sorry about that, it'll be back to normal in the next release.

It's been the OWL for some time now... One of these days I may even get around to writing the code required to make sense of the name change