That's not the behaviour I see here when all cameras in a CWL group get deleted... The below screengrab shows the state of my CWL after setting up a new group and adding two cameras to it, then deleting these cameras from a different WME session, and then rescanning the CWL from the original session:

http://i7.photobucket.com/albums/y299/t ... a46797.png

Despite all the cameras in that test group being deleted, the group still exists in the CWL and the deleted camera notifications are still associated with that group. Only when I click the "Remove deleted" button does the group get removed from the CWL. Note that the group will still be present in the drop-down list - the only way to remove a group from that is via the "Delete group" button.

Just checked it in Chrome as well (above screengrab was from Firefox), and the behaviour is the same. If you're able to recreate the problem, please can you leave the deleted cameras in the CWL and then send me a copy of your URO+ settings (via the Backup option in the Misc tab).

Thanks, but unfortunately as you've guessed, placing the camera into a new group has indeed overwritten the data I was interested in.

If you find any cameras that you definitely know are bogus, then you can try forcing the bug by deleting them yourself. First add the camera to a CWL group as normal, then reload WME to make sure the CWL changes have been saved. Now delete the camera using the standard WME delete tool - DON'T use the delete camera link in the URO+ popup, as this automatically removes the camera from the CWL as well... Then reload WME again and check the CWL to see if the deleted camera has been pushed back into the no group category.

This is a known issue with the interaction between URO+ and Toolbox versions below 1.3.7.3 - please confirm which version of Toolbox you've got installed.

qwaletee wrote:It mysteriously started working for me now.

I would like to see a simple option to temporarily disable all the options without having to reset them individually each time, if that's doable. Also, some of the Yes/No options are confusing, is there documentation on them? I may not have skimmed enough of the 34 pages in this thread

I think everything has been documented to some extent as and when that particular option/feature was introduced/revised, but there's no single point of reference for the script, no. Unfortunately, as the script has evolved/mutated/turned into something far removed from its humble beginnings a year and a half ago, I haven't been placing as much emphasis on consistency of operation as I perhaps ought to have.

When I get some time to mess around with the code again I'd like to work on tidying up the UI a bit, but that isn't likely to be for a while yet - the only coding I have time for right now is the stuff that pays the bills...

dbraughlr wrote:It would be handy now to have a checkbox to suppress all type Missing landmark URs.

Do you have a permalink to any of these mysterious creatures? I haven't seen any on the maps here in the UK.

dbraughlr wrote:If you go to https://www.waze.com/livemap/, you may make a missing landmark report at someplace that is suitable to you.

Thanks, I'd forgotten that was one of the UR types available from the livemap... I've now got the data I need, support for them in both URO+ and LMUR will be added *ahem* soon

*sigh* it's either been a *lot* longer than I thought it's been since I was last in the beta editor, or there's been some pretty significant changes released with minimal time given to fully test them, because last time I checked URO+ was working just fine in the beta... Given the seriousness of this, I'll look into it ASAP - unlikely to be before the weekend though.

Twister-UK wrote:*sigh* it's either been a *lot* longer than I thought it's been since I was last in the beta editor, or there's been some pretty significant changes released with minimal time given to fully test them, because last time I checked URO+ was working just fine in the beta... Given the seriousness of this, I'll look into it ASAP - unlikely to be before the weekend though.

Just noticed in the WME release notes topic that the "let's rip everything up and start again, breaking URO+ in the process, oops" version of WME is currently only available in the US/Canada, which probably explains why I hadn't noticed any problems in either beta or production editors recently...

Unfortunately, although I can use the practice mode to start investigating the changes, URO+ won't run in practice mode without modifying the way the script integrates with WME (which isn't something I really want to be doing whilst also trying to fix the problems created by this new version of WME), so a fix may not get released until the rest of the world gets the new version.