Good. I'll do an extended click test
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
You are both right. Simply the icon's active area remains between the comment bubbles (their blocking areas are actually rectangular) and the popup rectangle and a rectangular area over the icon, to the left from the popup window. Pretty enough if I know where to deterministically click
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
When using the popup's "Open in new livemap tab" link from the beta editor, the newly created tab will contain a nonfunctional link https://editor-beta.waze.com/livemap/...
Could the initial editor-beta. be automatically replaced with www.?
Could the initial editor-beta. be automatically replaced with www.?
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Ah, and this. Me too.elljay23 wrote:Just a "me too" for not being about to hide URs in latest Chrome (31.0.1650.63 m) and URO+ 3.4 with the latest make over of public WME.
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Regarding CWLs, I've a couple of times seen a probably bogus camera, so I've always created a new geographically named group for it (to immediately know, where it was placed) and inserted the camera there.
After some editor recognized the camera as indeed bogus, he deleted it. Now URO+ reports me that "One or more cameras on your watchlist have been modified or deleted!" - so far so good. But although the camera still exists in my list (albeit red highlighted) and URO+ still can pan the map there, its group is already deleted and the camera is placed in the "No group". Could the group persist until I'll delete it manually? Or at least until all red DELETED cameras disappear after myself pressing the "Remove deleted/all" button?
After some editor recognized the camera as indeed bogus, he deleted it. Now URO+ reports me that "One or more cameras on your watchlist have been modified or deleted!" - so far so good. But although the camera still exists in my list (albeit red highlighted) and URO+ still can pan the map there, its group is already deleted and the camera is placed in the "No group". Could the group persist until I'll delete it manually? Or at least until all red DELETED cameras disappear after myself pressing the "Remove deleted/all" button?
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
I see. And do believe. Just that I've been facing this problem twice during last ten days or so, thus I've been thinking of a behavioral problem.
I'll check it again after spotting any cameras again.
Sent from a touch display, which took care of perfectly scrambling my thoughts.
I'll check it again after spotting any cameras again.
Sent from a touch display, which took care of perfectly scrambling my thoughts.
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
I still do have the last deleted camera in the CWL, just after reporting it, I've created a new list (named a sort of "Deleted Cameras") and shifted the deleted one there. I can imagine it could have damaged what you were interested to see
I'm sending you the settings per PM.
I'm sending you the settings per PM.
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Today I've found some 7 more bogus looking cameras and sorted them in, I'll let you know as soon as some gets deleted.
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
It has stayed in its category.
But I'd swear...
I'll be back, if it happens again.
But I'd swear...
I'll be back, if it happens again.
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Upon hovering mouse cursor over a camera, the popped up dialog window states, among other info, e.g.: "Speed data: 50kph".
May I ask to modify the speed unit to "kmph" or "km/h"? I'm really missing the "m" there (and read it as kilopondhours)
May I ask to modify the speed unit to "kmph" or "km/h"? I'm really missing the "m" there (and read it as kilopondhours)
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Re: [Script] UROverview v2.02 (20131111)