Taco909 wrote:Ya...
On Zoom level 2, I can see nothing older than 19 days, On Zoom level 1, I can see nothing older than 9 days, Zoom 3 opens up to 30+
I had never noticed this progressive loading of older URs and I'm sure I've seen "red" tags at wider zoom levels before. Maybe this was a part of the latest WME changes?

Could be another phased rollout of new and "improved" features across the different servers - WME on the international server was still dishing out URs of all ages at all zoom levels, so perhaps this age/zoom link is only active on the US server at the moment... When I get a chance, I'll compare servers and see what's what.

KuniaKid wrote:Places tab conflicts with Places Tools. Any way to resolve?

Didn't even know that script existed... When I get time I'll see what the conflict is and how best to resolve it.

Twister-UK wrote:

Taco909 wrote:Ya...
On Zoom level 2, I can see nothing older than 19 days, On Zoom level 1, I can see nothing older than 9 days, Zoom 3 opens up to 30+
I had never noticed this progressive loading of older URs and I'm sure I've seen "red" tags at wider zoom levels before. Maybe this was a part of the latest WME changes?

Could be another phased rollout of new and "improved" features across the different servers - WME on the international server was still dishing out URs of all ages at all zoom levels, so perhaps this age/zoom link is only active on the US server at the moment... When I get a chance, I'll compare servers and see what's what.

I just checked the US server, and when fully zoomed out I was able to see URs over a month old, so still not sure why you're seeing a difference based on zoom levels

3.19 now includes an option (tucked away on the Misc tab) to disable places filtering, which then allows full use of the WME Places Tools add-on (which it seems most of us were completely unaware of until KuniaKid mentioned it just a few posts ago...). It also fixes the UR and Problem popups in the latest WME Beta.


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

No, that's never been an option. What you might be thinking of is the behaviour when the position of the UR/camera/etc would normally cause the popup to be rendered partially/completely off-screen, at which point URO+ tries to position it as close to the required position as possible whilst also keeping it completely on-screen.

Popup positioning is always a bit of a fine balancing act, because whilst obscuring stuff isn't a great idea, neither is being unable to mouse-over the popup because the pointer-popup gap is so large that you can't move the mouse fast enough to avoid triggering the popup closure code... Perhaps I've tipped the balance slightly too far in favour of allowing popup mouse-overs with this release, I'll play around with it some more for the next version.

3.20 introduces the following changes/updates:

• Added option to hide all open URs (requested by Taco909)
• Added option (in Misc tab) to inhibit the "UR has pending questions" prompt (requested by pumrum)
• Improved positioning of the UR/MP/camera popup (requested by pretty much everyone )
• Removed a couple of JS console errors

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

voludu2 wrote:I was talking to another editor about recent errors while editing, so I used "F12" to pull up my javascript console.

I saw this error. Of course, the first line is not an error; I only included it for debugging info. The second line is the error:

URO+: added SRS event handler wme_uroverview.3.19.user.js:164
Uncaught ReferenceError: uroInitiateRefreshAMObjects is not defined wme_uroverview.3.19.user.js:2973

Thanks, that one's been nuked along with another one I noticed whilst dealing with this one...

manoeuvre wrote:"UR has pending questions" how does this work?

Does it look for ' question mark = ? '

No, it intercepts the call WME makes to the function used to generate the "UR has pending questions... OK/Cancel" requester, then compares the text WME has asked to be printed in the requester against the appropriate translation string, and inhibits display of the requester if the two match. Otherwise it lets the requester display as normal - e.g. if you try closing the WME tab/window when there are unsaved changes.

FID mismatches are generated when you mouse over a different object to the one that'd been generating the last popup, it's just URO's way of letting you know it needs to generate a new popup so nothing to worry about.

The uncaught typeerror messages are more of a concern, and do suggest something is changing behind the scenes. Thinking about it, the other console error I fixed whilst checking the one you pointed out is one I haven't seen before, so perhaps that was just the advance scouting party with the rest of the damned things following on a few days later...

3.21 is an attempt to address the compatibility issue with WME Toolbox. I describe it as an "attempt" only because I don't understand why having WMETB installed is causing the issue, and although 3.21 no longer appears to cause problems there's always the possibility it still exists in some unusual cases I haven't seen during testing...


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