3.51 introduces the following changes:

• Added master enable checkbox to allow instant toggling of script activity
• Keyword filtering for URs now searches in comment text as well as descriptions
• UR stacks containing closed URs are unstacked without gaps if WME is switched into hide closed URs mode
• Various compatibility fixes for latest WME Beta release...

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

CBenson wrote:I'm having a problem that I'm not sure whether is user error or not. When I enable URO+ all my cameras disappear. I have nothing checked on the camera tab. I can't find a setting that displays the cameras for me. Am I missing some setting somewhere?

About half of the options on the cameras tab are of the "tick to show/untick to hide" variety, so if you really do have nothing at all ticked on that tab then each of those options will be acting to hide their corresponding type of camera, and the combination of having them all acting together means there aren't any types of camera that would remain visible.

To set up the cameras tab such that it's performing no filtering whatsoever, make sure that only the following options are ticked:

Show Cameras by creator:
world_* users
usa_* users
other users

Show Cameras by approval status:
approved
non-approved

Show Cameras by type:
Speed
with speed data
with no speed data
Red Light
Dummy

3.52 was just going to be a bugfix update, after I noticed UR filtering wasn't being disabled when the master enable switch was turned off (although I'm certain this was working when I first implemented the switch ).

In response to the above comments regarding place popups, I've now also implemented a mouse motion-sensitive timer to prevent popups (of any flavour, not just places) from appearing until the mouse has been stationary for a definable period. The setting for this - "Mouse idle" - can be found on the Misc tab in the "Popup timeouts" group. Eagle-eyed users may also notice the existing timeout has been renamed to "Mouse over"...

This isn't necessarily the final version of the fix for this problem, it was just something I could quickly throw in as part of getting the above bugfix released sooner rather than later. Those of you who've had difficulties with the places popup, please play around with this new timer setting and see if it helps you out. If not, I can look at trying some of the other ideas mentioned previously when I've got more time to do so.


As a bonus, whilst testing the master enable fix, I also identified what I now think has been a long-standing bug which I'd only noticed so rarely that I'd always dismissed it as just a random interaction between my code and WME, whereby from time to time any UR which had been tagged with a yellow (has my comments) conversation bubble would revert to using the green (none of my comments) bubble instead. The fix for this bug also optimises the custom marker rendering code a bit, so bonus on top of bonus


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

bz2012 wrote:In order to set the time delay (and have it passed along to a spawned tab) I had to set and "back up" the settings. Before I did that, the open in new tab window took the old 'default' time setting, not the newer setting.

This has always been a limitation of the way the script handles settings - they're only flushed into the browser localStorage when you close/reload the tab in which the settings were changed, or you force the script to flush them via the backup/restore functionality as you've noted above. If you therefore open a new WME tab/window whilst the original one is still open, the URO+ instance that runs in that new tab/window will be using whichever settings had last been flushed by the original instance, which won't necessarily be the same as the settings currently in use by that instance...

Improving the cross-tab/window behaviour of the script is something I intend to work on in the near future.

bz2012 wrote:To start the timeout clock 'ticking' for the pop up, the mouse must be completely stationary.
It is NOT sufficient that it be held in the same area, I must take my hand off the mouse and be careful not to disturb it.

I can look at adding in a distance threshold so that small movements don't reset the timeout.

bz2012 wrote:I am not sure WHAT 'centers' places on the screen when they are selected but I want to disable that centering as I scan my edit area for places in a grid and it loses my place when the an item centers itself on the screen. I am able to disable the centering of URs and MRs but not places. It may be some other extension that is doing this.

If you mean PURs rather than places themselves, this is a native WME "feature". If you really do mean places, then it's some other script - URO+ only recentres the map view if you explicitly ask it to do so via one of the popup links, it won't do anything if you click on the native marker itself.

bz2012 wrote:I thought that No on these:

If last comment made by me?
If last comment made by UR reporter?
...
used to override this one
Last comment less than x days ago
....
and others. Apparently the No's no longer override suppression due to other conditions.

Correct, nor should they ever intentionally have done so in previous versions. The sole purpose in life of the UR filtering process is to hide as many URs as it can. Therefore the only way to prevent a UR from being hidden is to alter your filtering settings so that none of the selected filters are being triggered - it doesn't matter how many of the filters you've got active would allow the UR to remain visible, it only takes one filter triggering to hide it.

Not necessarily saying this is how it works in reality, as there are so many combinations of filters it's entirely possible that certain specific combos do end up interacting with one another unexpectedly. But if you treat the filters as being completely independent and ask yourself "would this filter setting on its own cause the UR to be hidden", then you should usually come up with the same answer as URO+ does. If you don't then I'd like to know about it so I can put in a fix...

In the context of these particular filters, yes and no define which way round the filter will operate - e.g. will it hide all URs that were commented on by you, or will it hide all URs that weren't commented on by you? - so with either option checked the filter is active. By providing the third choice - unchecking both options - it allows this filter to be deactivated.

3.53 brings the following changes...

• When the master enable switch is turned off, URs which don't have comments no longer get given native comment markers...
• Small amounts of mouse movement can now be ignored when timing how long the mouse is idle before the popup is shown
• Marker unstacking is now also delayed by the mouse idle period
• URs outside the editable area can be hidden
• Current script settings are now applied to new tabs opened via the popup links

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

taco909 wrote:Even if I have the Places layer shut off, the popup appears over any area place in a part of the map where I had the Places layer open during that session.

Is this the same popup each time, or a different popup depending on which place was at that location?

When you mouseover the area where the place was, do you see any visible change besides the popup appearing?

Does this only occur when you've got backfilling enabled?


This sounds like a particularly weird bug, as URO+ is looking at the places layer to see which one (if any) is currently highlighted and therefore where it should place the popup - for it to be displaying the popup in the correct place but without the place actually visible seems to imply that something has gone nuts behind the scenes in WME itself, causing it to still be changing the highlight state of the places despite the layer being hidden. Take it as read that I haven't been able to replicate this yet...

3.54 fixes the problem where the places popup would chase your mouse pointer around an area place, and also auto-closes the camera popup when the Delete Camera option is used.

It also marks the first use of the JSHint tool which identified rather more things requiring attention than I'd like to admit to... It's entirely possible that some of the things identified and fixed here have been responsible for some of the weird behaviour some people have seen with the script, and if not then at least the code is now in a far better shape than I thought it was.


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

jemay wrote:Ok, I have updated to the latest release (UROverview Plus 3.54(dbg)) FF and I am getting a strange filter but no filter process on two different machines.

So it applies the filter. I move the map the appropriate ones disappear then they re-appear, but when I turn off URO+ (Uncheck "Enabled") and then turn on URO+ (check "Enabled") the appropriate ones will disappear. I then move the map again it starts all over (appears, uncheck, check to make them disappear)

Which filters are we talking about here? I've done a quick test of UR filtering on both the RoW and USA servers, with and without backfilling active, and that seems OK, so is this a problem with one of the other types of filterable things, or something you're seeing generally across all types? Also, are we talking about WME production or beta?