Thank you, Vince!
Seeing many examples in the UK where URs are showing roundabout direction icons as anticlockwise, this is opposite to the direction we drive. I believe there is/was a report in Centercode [BUG-8577] for similar in the client but Iām unsure if this is directly showing what was displayed in the client.
Permalink 1 | Permalink 2 (closed UR)
I know you have no way of knowing this, but in one of my former lives I was the department manager for an entire staff of software support desk personnel, responsible for a 24/7 call center whose clientele was exclusively North American electric utility operations centers.
Suffice to say, I am unusually well qualified to understand how software help desks work, I even designed the architecture of the support ticket system we had for tracking and assigning issues. I absolutely understand how problem replication is critical to understanding and fixing a problem.
That means I also understand that when a problem is universally happening everywhere, and we have already plainly described what is occurring (segment data doesnāt refresh when panning, and new segments whose initial endpoints pan off screen donāt create JNs), sorry but I feel quite justified in questioning why you would also ask for PLs. The issues are everywhere, not locational, and not unique to specific circumstances.
Actually listening to what the user is reporting should color your next steps and help you determine how to investigate further. Just asking for PLs all the time suggests youāre not paying attention.
Sorry. End rant.
Iāll restate how to replicate, as simply as possible.
Open WME in an incognito window.
Zoom in to level 7 or 8.
Adjust some segment geometry, pan the map, and start trying to select JNs as you go. It will not be long before you find āunselectableā JNs.
Save and soft refresh solves the problem.
This is new and undesired behavior.
Open WME in an incognito window.
Zoom in to level 7 or 8.
Start a new segment by snapping the start point to an existing segment. Continue your new segment sideways, and draw it long enough that you need to pan the screen for nearly its full width two or three times. Upon save, you will likely get a save error warning of possible disconnection (because a new JN was not formed at your start point).
This is new and undesired behavior.
I have reported this in Beta Bugs (minus the grayed out area part), including a video of the issue in WME Beta.
Lastly, while we have already described what is going on with unselectable JNs and how to replicate, here is a video of the problem occurring with active scripts. The scripts are not causing the problem, but they sure are reacting to it in far more visible ways, making a much clearer visual representation of the problem.
First I just pan around. No problem. Then I add a geometry node and then delete it. Continuing to pan around with those unsaved edits reveals grayed out areas where data isnāt loading, and the Magic script starts highlighting all the resulting errors.
https://www.youtube.com/watch?v=CCMK8s6EuS0
Basically, if you have any active unsaved edits, segment data quickly stops loading as you pan around, and sometimes it occurs even without active edits. This happens with or without scripts, but the scripts make it a lot more obvious. I suspect that the two issues (unselectable JNs, and not generating new JNs off screen) are actually rooted in a single problem.
As stated before, this kind of error is not locational or tied to any unique map data circumstances, which is why PLs are utterly irrelevant.
1 Like
Or always relevant, meaning you can take any PL you want and it will happen eventually 
Thank you everyone, we have opened an internal issue.
Best,
Maia
Myself and another editor have both been unable to save new MTEs - the Save button is blue, but nothing happens when clicked. We narrowed it down to the event name being too long - this previously gave an error message, but that error message is no longer happening.
See the new UI in the latest WME version release thread:
https://www.waze.com/forum/viewtopic.php?f=8&t=309987
1 Like
Any word on progress on this?
Having to soft refresh nearly every time you pan around is extremely frustrating, and there is a LOT of panning going on during the Falcon Raidā¦
Hi everyone,
This issue is still open internally. We still donāt have an ETA for the fix, sorry for that.
The dev team has provided a workaround in the meantime: to unselect the segment before panning the map.
Weāll update you if we have any news.
Thanks,
Maia
FYI, unselecting a segment before panning does not appear to help anymore.
I retract my statement. unselecting the segments before panning does still appear to help BUT if you have something selected and move the map even a few pixels the bug shows itself most of the time.
1 Like
I was completely unaware of this workaround, had not even been aware of this being part of the root cause. Thank you.
1 Like