Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.
Post by Olestas
Also cannot close URs, dialog remains open, and cannot create speed camera.. it keeps mouse tied to speed cam..
Probably it is all tied to new api.
viewtopic.php?f=819&p=1849886#p1849886
Olestas
Waze Global Champs
Waze Global Champs
Posts: 6666
Has thanked: 1560 times
Been thanked: 1109 times
Send a message

Post by Olestas
No, just update it to 3.8.6
Olestas
Waze Global Champs
Waze Global Champs
Posts: 6666
Has thanked: 1560 times
Been thanked: 1109 times
Send a message

Post by Olestas
Yes, same issue. COuld you please check.
Olestas
Waze Global Champs
Waze Global Champs
Posts: 6666
Has thanked: 1560 times
Been thanked: 1109 times
Send a message

Post by orbitc
Fabianotkd wrote:I just discovered the script that blocks WME...
UR-MP Tracking... :(
I don't know why but it slows WME...
Any other the same problem?
you don't need to run it all the time. You can run a report and work with that. Based on the amount of reports around you also a factor for that. YOu can choose to show less or smaller area. Please try to play with its setting.
orbitc
Waze Global Champs
Waze Global Champs
Posts: 6576
Has thanked: 946 times
Been thanked: 4916 times
Send a message
Regional Coordinator for Northeast & New England
•Tier1 •USA Coordinator •Global Champ & Mentor
•iOS & WME ßeta Tester •Beacon, CCP & Wiki Master
•Master Raiders •Localization •Content Raider


USA | MapRaid!

Post by papok
I could not import a WKT file. It asks me to choose I file even after selecting one and having it name behind the select file button.
papok
Waze Local Champs
Waze Local Champs
Posts: 880
Has thanked: 110 times
Been thanked: 288 times
Send a message

Post by papok
BUG. With a clue.

Sometimes the scan stops and I get an error at the console:
Uncaught TypeError: Cannot read property 'lon' of null (program):3776

It may happen at any stage of the scan...
Most of the time it is solved by switching the window from "Maximize" to "Restore" and vice-versa (because it may happens with both modes).
I haven't tried to re-size the window instead of maximizing it though
It is a very large area (over 157'000 Km2) but with very low activity. So this error may happen with the same UR's that the day before caused no problems.
I guess is related to the scanning at the edges of the area... may be some number rounding... but not necessarily in the first row. Last time it happened at 43% of the scan.
papok
Waze Local Champs
Waze Local Champs
Posts: 880
Has thanked: 110 times
Been thanked: 288 times
Send a message

Post by papok
Confirmed (once)

So, disabling the distance checking during scan end re-enabling it after it would patch (not fix) the code. And may be accelerate by some milliseconds...
papok
Waze Local Champs
Waze Local Champs
Posts: 880
Has thanked: 110 times
Been thanked: 288 times
Send a message



Post by PealRinger
Thank you again for your efforts with this script. Unfortunately since the new WME version yesterday I am having a couple of other issues when running this script:

* Updating two-way speed limits
When you add both A-B and B-A speed limits only the edit for one direction is recognised and gets saved, leaving the other speed limit blank.

* Drawing new roads
When you draw new road and terminate it with a double-click the cursor remains as a circle and you need to press 'Esc' to be able do any other edits.
PealRinger
PartnerCoordinator
PartnerCoordinator
Posts: 1984
Has thanked: 226 times
Been thanked: 696 times
Send a message