Just an update, I confirmed, at least on my computer, that Add-On's was the source of my problems with UR/PRs not changing color. I installed the latest version, and the icons stopped changing color again. Deactivated it, and they started changing color again. No clearing of cache/cookies.
So what is the plan for the new street numbering system in NA? Will these actually start being used by the Waze app for locating addresses? Or is this like with the old numbering system, where Waze doesn't use it, so the only reason to adjust the addresses was for some "vague" future that may or may not actually use the information?
Hello, I can't save a new rodad if you don't have a choice in the city of the tab. on several occasions its is necessary between citys. I have read the topic looking for the same problem but not the found.
HoustonMG
HoustonMG
It's the same problem, that road no have city and the new editor not permit. same times I save the road, next edit and save ad only the country then work same time.earrieta wrote:I am having the same problem. Cannot save a road segment without putting a City name. It will not accept the 'No City' option. This is necessary in this case as the road is well in the countryside.jasonh300 wrote:Be sure you're following these instructions (and you should be familiar with that entire section of the Wiki before adding new roads).houstonmg wrote:Hello, I can't save a new rodad if you don't have a choice in the city of the tab. on several occasions its is necessary between citys. I have read the topic looking for the same problem but not the found.
HoustonMG
http://www.waze.com/wiki/index.php/Road ... _red_roads
https://es.waze.com/editor/?zoom=4&lat= ... TTTFTTTFTT
creo que tu hablas español. esto esta pasando a menudo, esperemos que se solucione.
OK, I know it's a little out of place here, but I'd like to post positive feedback for the new editor.
Roundabouts are no longer created with soft-enabled turns. Since it's extremely rare for a roundabout to have a disabled turn, creating them with hard-enabled turns covers the vast majority of editing cases.
Roundabouts are no longer created with soft-enabled turns. Since it's extremely rare for a roundabout to have a disabled turn, creating them with hard-enabled turns covers the vast majority of editing cases.
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets
I want to go to a commune in Vermont and deal with no unit of time shorter than a season
My scripts: WME FixUI WME Presets
I want to go to a commune in Vermont and deal with no unit of time shorter than a season
There is a new version, posted here: New version deployed - v1.0-41bz2012 wrote:I don't see any official announcement of a new roll out.
Whilst my editable and driven areas are showing, a quick test shows that they don't seem to be updated as I pan the map: after panning I have to refresh to see the editable areas on the newly-revealed map. Try clearing your browser cache?ohad-ron wrote:Changes:
- Make the currently active UR / problem more visible
- Fixed a bug where selected segment details did not show in certain scenarios (landmark layer activated)
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets
I want to go to a commune in Vermont and deal with no unit of time shorter than a season
My scripts: WME FixUI WME Presets
I want to go to a commune in Vermont and deal with no unit of time shorter than a season
Quite, I noticed I'm also unable to type any number (also usiung FF)..AlexN-114 wrote:YesDimanZ1 wrote: I do so, but it is uncomfortable.
Dumdeedum
This is my signature, it is very informative don't you think?
This is my signature, it is very informative don't you think?
Once again, a WME release has been deployed that is NOT the same as the beta was.
The arrow functionality looks the same as it did in the Beta, but it does not work. If you hit A to dim the arrows and make them unselectable, and then change zoom levels, the arrows become selectable again.
Furthermore, after this has happened, hitting A no longer works at all. So you're stuck with these giant arrows in the way of doing any kind of editing, or you have to do a permalink to start all over again.
This makes the editor completely unusable. This wasn't an issue with the Beta editor. If you're just moving the Beta over to the WME server for use without any last second untested tweaks, why does this happen? There seems to be an issue like this with every new release.
Also, I never brought this up before, because I thought the new arrow style was just some kind of horrible experiment and it would never make it to the public release: anyone who is red/green colorblind (we have several of them) will not be able to differentiate between the red and green arrows. That's why the other ones had the little checkmark in them when the arrow was green.
With all the things wrong with the editor, why are the developers wasting time changing something that wasn't broken to begin with? Was it really necessary to redesign the arrows just to get that little ? to show when there's a soft turn?
The arrow functionality looks the same as it did in the Beta, but it does not work. If you hit A to dim the arrows and make them unselectable, and then change zoom levels, the arrows become selectable again.
Furthermore, after this has happened, hitting A no longer works at all. So you're stuck with these giant arrows in the way of doing any kind of editing, or you have to do a permalink to start all over again.
This makes the editor completely unusable. This wasn't an issue with the Beta editor. If you're just moving the Beta over to the WME server for use without any last second untested tweaks, why does this happen? There seems to be an issue like this with every new release.
Also, I never brought this up before, because I thought the new arrow style was just some kind of horrible experiment and it would never make it to the public release: anyone who is red/green colorblind (we have several of them) will not be able to differentiate between the red and green arrows. That's why the other ones had the little checkmark in them when the arrow was green.
With all the things wrong with the editor, why are the developers wasting time changing something that wasn't broken to begin with? Was it really necessary to redesign the arrows just to get that little ? to show when there's a soft turn?
This is not happening. When you solve a UR or MP, the icon does not change. Same if you mark it "Not Identified". The icon stays exactly the same, and when you hit Save, it just disappears.ohad-ron wrote: This is how it should look:If you're seeing anything different then it is a bug.
The arrow dimming glitch is now fixed, after clearing cache again. And it looks like the colorblindness issue has also been solved.
https://dl.dropbox.com/s/lr5spvy90kswevd/colorblind.jpg
Right now, since the latest fix, it seems to be behaving exactly as the beta did (with the exception of the house number complaints, which I have not yet tried in WME). Also, the little (X) on the restricted turns never appeared on the beta that I know of.ohad-ron wrote:It is the exact same version of the code. There might be some configuration differences between the two deployments, but in 99% of the cases it should not (and did not) have any effect. The testing work done on the beta was extremely valuable to us. I think we managed to iron out most of the major issues... I hope in the next few days we'll be able to fix the issues people are still encountering.fvwazing wrote:Ohad?jasonh300 wrote:Once again, a WME release has been deployed that is NOT the same as the beta was.
Thanks everyone for the issue reports - we are watching this thread and fixing them.
Re: New editor version - V1.0.12 [NA + ROW]