It would be useful to see unapproved cameras at higher zoom levels.
Currently they are hard to find unless you happen to be at the right location in the right zoom level.
It would be useful to see unapproved cameras at higher zoom levels.
Currently they are hard to find unless you happen to be at the right location in the right zoom level.
Even another one or two levels would be good just to get an idea where to concentrate on.
Sent from my GT-I9100 using Tapatalk 2
Compatibility update for the latest WME beta, allowing users to log-in again (beta code seems to be constantly trying to load layers data whilst waiting for the user to log in, which was then tripping the URO layer event handlers over and over and over again, blocking access to the login UIâŚ)
Another compatibility update for WME beta⌠yet again the layer IDs have been tweaked ever so slightly for no reason that is instantly obvious - why keep doing this Waze, WHY???
Also taken the opportunity (having forgotten to deal with it in the last few updates) to get rid of the tiny blue overview box that used to lurk in the top-left corner of the WME window on startup.
Was that you? I wondered what the heck that wasâŚ
Just a little question: is it possible to show the userid of the âurequesterâ?
Paolo
Unfortunately it is unknown. We are asking Waze to reveal it (or let us at least communicate with him, while keeping him âhiddenâ).
Was this the same blue box as Show URs/map problems (LMUR v0.6) displays in the upper left map corner?
Was this the same blue box as Show URs/map problems (LMUR v0.6) displays in the upper left map corner?
Quite possibly, since adding UR/problem popup support into LMUR was pretty much a cut-n-paste operation from whatever was the latest version of URO at that time⌠Iâve got some more changes planned for LMUR over the next couple of weeks, so if there is anything like this which needs fixing Iâll deal with it then.
Not sure, but there may be a bad interaction between this script and the latest WME version. With this extension enabled scrolling is far too fast. Disabling the script seems to resolve the problem. Obviously this is far too an important script to miss out on for too long!
Not sure, but there may be a bad interaction between this script and the latest WME version. With this extension enabled scrolling is far too fast. Disabling the script seems to resolve the problem. Obviously this is far too an important script to miss out on for too long!
You havenât reverted to a pre-1.8 version by any chance? Firefox/Chrome + Public/Beta WME all still seem OK here with 1.12.
I had the scrolling issue too, but just updated the script and seems to be ok nowâŚ
This is causing a problem with the display of approved speed cameras with the latest WME update. They disappear from the map.
Nope, definitely on 1.8!
When I click on a UR with the script enabled, it zooms in but the zoom bar in WME stays on furthest out zoom, donât know if that helps.
Uninstalled, reinstalled and so far, ok âŚ
Small update to re-enable operation in WME Beta, and to fix - hopefully once and for all - malformed livemap links which some users are experiencing (thanks to zannax for bringing this latest variant of the problem to my attention).
This is causing a problem with the display of approved speed cameras with the latest WME update. They disappear from the map.
I havenât been able to replicate this. Please check the URO filtering options to make sure the âshow approved camerasâ checkbox hasnât been cleared, and if everything looks OK there then try re-installing the script.
A request for a minor functionality change.
When filtering URs including/excluding a particular string, could that be done case-insensitively?
Weâve got a few URs posted in the South London area for roadworks, but the work âroadworksâ appears in a mixture of cases, so itâs not so easy to filter them.
When filtering URs including/excluding a particular string, could that be done case-insensitively?
Done, 1.14 adds a âcase-insensitiveâ checkbox which applies to both present and absent keyword filters.