Functional version of this script adaptated to the new WME layer menu:
https://greasyfork.org/cs/scripts/29448-wme-livemap-alerts-overlay-beta-fork
Says script could not be found. Could you possibly repost?
Sweet! Thanks a lot it works great 
Thank you for this script!
Since the release of WMEv2.0 this script stops me from selecting or hovering over items (segments, places, cameras etc) within the map area on first load. I am still able to drag the map and use the control. I must first use a menu to add a new item to the map, this then allows me to select again. I can cancel adding the new item and still able to select again.
OSX - Chrome Version 62.0.3202.94 (Official Build) (64-bit) - All other scripts disabled.
Yeah, i have similar symptoms too. But it started lately than released the first version of WMEv2.0, I think first problems we (I and some colleagues from community too) have seen last week. And this problem occurs very rarely to me. And I can not figure out, where the problem isâŚ
When you disable the script layer from layers menu, then hovering and selecting then works? And if you enable it again, will stop working?
this script has stopped working since yesterday
Except the problems described in previous posts I have no other issues. Can you specify it please?
in addition, it has completely stopped working
Iâve made a new version 5.11 with some bug-fixes, including the annoying one described here, which caused the impossibility of selecting elements in WME.
I know, how I fixed the bug (setting the ZIndex before adding layer to map), but still donât know, why it ever occursâŚ
If you still have a problem with that, please let me know!
New version 5.12 released. Except the fix for missing Waze object I have added also the option for control the LivemapAlerts layer with keyboard shortcut. The shortcut you can set in WME keyboard shortcuts menu.
posting so i remember to install this
Doesn not work. New livemap release.
Even if I see the new livemap, the script is still working correctlyâŚ
Hi gang, script is back and kicking!
The script is already back more than a year and half ago as says this thread.
I have also added to it some new features.
https://greasyfork.org/cs/scripts/30581-wme-livemap-alerts-overlay
Nice, thanks!
I am receiving this error in Chrome. Commenting out lines 464-468 which is the call to the function âregisterKeyShortcutâ lets the script load. In line 420 if you put a letter/key combo it also allows it to load. How can I fix this so I donât have to manually add a key to the script and have no errors when loading? Iâd like to be able to just toggle it on and off through the layers.Uncaught Error: Missing key in shortcut
at Object.fromEmacsNotation (app-88312eb53b2417aa384e.js.gz:1:900939)
at Bt.registerShortcut (app-88312eb53b2417aa384e.js.gz:1:902947)
at app-88312eb53b2417aa384e.js.gz:1:903343
at Array.forEach (<anonymous>)
at Bt._registerShortcuts (app-88312eb53b2417aa384e.js.gz:1:903307)
at registerKeyShortcut (userscript.html?name=WME%2520LiveMap%2520Alerts%2520Overlay.user.js&id=71ed0791-f5fc-437f-8018-755d997588b6:421:18)
at Proxy.initializeLiveMapAlerts (userscript.html?name=WME%2520LiveMap%2520Alerts%2520Overlay.user.js&id=71ed0791-f5fc-437f-8018-755d997588b6:465:3)
at St (<anonymous>:9:89)
at t.<computed> (<anonymous>:58:214)
at St (<anonymous>:9:89)
at r (<anonymous>:22:484)
at <anonymous>:23:112
at <anonymous>:67:445
at p (<anonymous>:67:464)
Lines 464-468:registerKeyShortcut("LiveMap Alerts Overlay", function(e) {
if (!roadGroupSelector.checked.disabled) {
checkbox.click();
}
}, "LiveMapAlertsOverlay");
Line 420 that doesnât have a keyboard shortcut:W.accelerators._registerShortcuts({[""]: keyName});
EDIT:
So it seems if you open the keyboard shortcuts list in WME and pick a shortcut, all of a sudden it works. Iâd recommend changing line 420 in this script to include a default shortcut or not throwing an error preventing loading the script if a default shortcut isnât picked. Iâve picked Shift+Q for now since that was not used.
EDIT 2:
So even if I have it disabled in layers (unchecked), every time a new page loads, the layer is back. I have to enable and disable the layer in the layers menu to get it to go away again. That one Iâm not sure how to debug/troubleshoot myself. Any ideas?
help,
it stopped working