dummyd2 submitted code for Redo Roundabout earlier today that ignores crossing segments that are not part of original the roundabout. We are currently testing for the next version.
Any editors below L5, currently does not have the ‘cure the soft turn or unconfirmed turn function’ and most of us are not aware of our mistakes.
May I humbly request that this function considered it for Area Managers in the next update WME Toolbox 1.5.9
Would again like to give special thanks to doctorkb, BellHouse and giovanni-cortinovis and the rest of the development team for providing such a helpful script for all editors to use. Your efforts in continuous improvement of the toolbox is amazing and shows your teams dedication to improving the Waze map quality around the globe.
Anyone below L5 can cure soft turns by selecting the node and pressing “Q” to use JNF. The restricted function will “cure” all soft turns within the map area, which can be very dangerous if the user hasn’t made sure that the restrictions are all properly set already. Often, soft turns exist where the restrictions haven’t been checked by an editor at all, so you should be analyzing each of these nodes anyway.
We also have the ability to specify features and rank/role restrictions by country on the roadmap for 1.6.0. At this point, we are assuming Champs will determine any deviation from the Toolbox defaults in their local countries.
To become aware of mistakes you need the highlight of these issues, and this is available from L3-AM level upwards. And as sketch already mentioned, the cure is available by the Q key.
I don’t know how long I have this issue but sometimes TB is not working fine with unconfirmed turns on a juction.
When I select the junction and press the Q key, it seems something is changed (segment become orange) but the “SAVE” button is not active and I cannot save the change.
I need to reload the page and remove the unconfirmed turn directly on the junction, without using TB.
Paolo
Next time you see such a situation, instead of fixing it directly, it would be better if you post a permalink here so the team can trouble shoot it.
Sent using Tapatalk for Android 4.4.2
I ran into a little glitch while looking at a recent drive:
Cannot pan map very well while viewing a recent drive with Toolbox enabled, at zoom=0
To reproduce
1 Enable toolbox
2 choose a recent drive
3 be sure to zoom out all the way
4 attempt to pan the map using mouse, arrows, or toolbox-enabled number keys
Observation: some panning might be possible, but you might be unable to pan to the end of a 1-hour drive.
To restore normal behavior:
- disable toolbox, refresh browser window, and try the above steps 2-4 again
?
Pans fine for me in Chrome. Anyone else seeing this issue?
I narrowed this down further. It only seems to happen if I have UR comments enabled AND the UR comments custom script.
I have pm’D rickzabel
i am not exactly sure what the issue is, but i am not seeing anything odd. my longest drive is 40 min and fits on screen when zoomed all the way out. i can mouse or arrow all over my visible area with a route shown.
I have pm’D voludu2 back 
Firefox.
Have not tried it with TB disabled.
I’ve also occasionally encountered a “fast pan” but have not started disabling scripts to try to replicate it because I CAN’T replicate it intentionally… I’d have to run script-less for a week, and even then I wouldn’t know.
What happens is the map will start panning multiple-times the distance that the mouse is moved. It is bad enough that even zoomed in, if not careful, I’ll end up moving the map 20 miles in one movement and have no idea where I am.
This an issue with URComments, when i redrew the new UR window to fit the screen it also affected the place and drive windows. to reproduce this drag the map but start under the drive window that is on the map. doing so will cause the drive window to be selected (highlighted blue).
in the version of URComments that has yet to go trough testing, i have removed most of the code that redrew these windows.
At present L3-AM and even L4’s are not able to see the soft turn and also the unconfirmed turns. As such editors have to press ‘Q’ at all end segments and also click segment by segment to check for soft turns.
I am appealing that this function be re-enabled for L3-AM’s and above.
I leave the decision to the Global Champs and also the toolbox development team.
I’ve just checked the code of the current Toolbox 1.5.8 again. The highlight of soft-turns is available from L3-AMs onwards, as said before. The highlight of unconfirmed turns is not restricted at all (except on dead-end nodes).
So if any L3-AM or L4 cannot see these highlights, I would suggest this user to re-install Tb and/or check if this is caused by some conflicting other scripts.
Thank you very much for the clarification and also the advise.
One last question, any reason for L3-AM’s and L4’s restricted from seeing dead end nodes.
Tried to request an unlock using the icon in the right bottom corner, but received the message “Your country is not registered in WME Fancy Permalink. Please, help me by sending me this number: 37 and a link to the unlock forum of your country to the Toolbox thread.”
Could you please add support for Belarus? For unlock requests we use the following thread: https://www.waze.com/forum/viewtopic.php?f=893&t=116763
Thanks.
I have been noticing that about 50% or more of the time I use toolbox remove unneeded nodes and save that it freezes up on the save and I have to start in another window. WME has done this a few times lately with other saves but most of them are with the toolbox remove extra node function. Just putting this out there for review and see if other editors are having this same issue.
Sent from my iPhone using Tapatalk
From time to time I have this problem but without using Toolbox.
Yup, will do. Will be available in next release.