I see they STILL have not fixed the bug where the “A” node does not always connect when adding a new segment.
Thankfully, URO+ has an option to completely suppress that waste of space.
What’s wrong with you, pointing out something like that?? You need to get your priorities straight! Of course they didn’t fix that. They were far too busy making superfluous UI changes to actually work on fixing some of the bugs… :roll:
(Gee, I’m not coming across too sarcastic or anything, am I? :mrgreen:)
Wow! Great! Updating segments… but…
There are some highways that are “mostly” underground: there are some intervals that have no solid “ceiling” for about 50 meters. Instead, they have a grid that allows ventilation, and sometimes the GPS could get signal. Should them be marked as tunnels or simply left as a small segments with elevation -1?
Unless that highway has other roads over/under it, it should be set to ground and the entire length be given the tunnel option. Even thought there are some segments that have some GPS signal for about 50 meters, travelling at highway speeds, you would be through it in a heartbeat. So just make it all one tunnel.
I wished they would give clear and proper instructions on how these features should be used vs forcing us to ask so many questions.
same issue with me
original WME menu have a “qoute like” look
where toolbox menu is completely outside the taskbar
and because of the new “black bar” at WME, we can’t open the drop down menu because it is simply disappear
100% agree here Rich. I don’t see anything gained what so ever by swapping the position of buttons or order of name attributes. I’d have to wager most edits are around the name/city and having those right next to the save button was very quick to work through updating remaining basemap. While it’s not a huge deal to move the mouse over a bit more, it’s more work than before and I’d like to think that we’d be evolving towards making things easier/quicker than harder/slower.
Please understand what this thread is for.
Yes, there is a problem with Toolbox and other scripts not working right now. There are some workarounds for that. HOWEVER, these issues need to be addressed in the respective scripts thread.
This thread is for v1.12 of Waze Map Editor. It has nothing to do with the scripts as Waze is not responsible for how they function with the updates. Please send and research any and all script related issues with the scripts thread.
You can find your scripts thread here
1 Like
It’s because of the city bar in the middle, annoyingly.
I like there being a more obvious display for the AMs than the old layer… though there might have been a better place for that. It is a pain to lose map visibility at the top.
Going to the oldest drive history, I see
When I switch between areas to display, the city name in the black bar does not change.
So until I zoom in one or two levels, it is displaying the wrong name for the area.
Waze knows about this issue, and we were told that it wasn’t considered to be a significant enough problem since zooming in again displays the correct name of the area immediately.
It’s not consistent though.
I don’t know from where on the screen it pulls the city name, but there have been many times that the central area of the screen I’ve been working has not matched.
Re the black city bar:
In Chrome you can remove it for the current session by:
- Right click the black bar
- Select “Inspect Element”. This should open a pane at the bottom of the Chrome tab with a <div> element highlighted.
- Right click the highlighted <div> element
- Select “Delete”
- Click the X in the upper right of the Inspect Element pane to close it
So when entering a Street Name the order is now changed to Street>City>State>Country but when entering the address of a place it’s still as before Country>State>City>Street.
Can that be consistent and made the same?
1 Like
I agree that specific comments about malfunctioning scripts should be posted elsewhere.
However, many scripts exist because the vanilla WME lacks critical functionality. For example, the Junction Angle Info script, or something that does its job, is effectively required to edit any but the simplest junctions. I would expect that the vast majority of advancing and senior editors run at least one script. Because the community must run scripts in order to use WME effectively, I believe it’s important that Waze be made aware when their modifications break those scripts.
We mustn’t complain to them about the specifics, but I think they need to know how heavily we rely on the scripts and how badly it affects community effectiveness when they break.
Time and time again, we have made it clear when an update kills a script. Script stability is now, and more than likely, will not be a priority for Waze Devs. That is why it’s up to the script/extension creators to be proactive and know what to expect when a script/extension breaks.
In a perfect world, the creators would have beta access, have full time to test things out, and, if things still haven’t been fixed, announce it on their thread the day the beta gets pushed to production. However, this isn’t a perfect world. People have lives. They can’t spend all their time making these things. The same can be said for Waze Devs. They have features and bugs to fix. They can’t be bothered every single time a script breaks.
The only time I can see if Waze Devs get involved is when a creator has tried everything, can’t get it to work, and contacts them for support.
My point is that some community scripts are essential features. If Waze breaks essential features while adding other features, that’s not necessarily a win for them, never mind us.
But that’s just it. It’s a community feature. Created by the community, for the community. If Waze was worried about it, they would hold off on moving from beta to production or integrate that script into the next WME update. But they aren’t because it’s not on their list of things to look out for.
And don’t forget : scripters are all VOLUNTEERS with a life and a work beside Waze !!! Give them time.
Thanks to be patient