Last night this was happening in NA server, but not on ROW server [long Road / Segments Layer load time] Chrome Said “waiting for tiles1.waze.com/*]. It is most likely due to heavy server load

juliansean wrote:Not sure if this is "known" or not, but with this new version when there is a street with the city marked "none" and you add an alternate city name the "none" checkmark goes away on the primary city name and you have to remark it.

megg2004 pointed out that State field on the primary name can also be automatically changed as soon as you click into the alt name box: . That's a dangerous, sneaky bug.

ranttine wrote:Selection engine is not working properly. Cannot select a new segment before unselecting the previous one. "Select all segments of street/roundabout" completely unfunctional. Loading up of road segments takes ages.

Occasionally can't move junction nodes. Occasionally can't delete segments. Not too happy with this version.

Some or all of these problems are almost certainly script-related. I've done some testing using "Select entire roundabout", but this probably also relates to "Select entire street" and the need to deselect one segment before selecting another. I have identified 5 separate scripts , all of which cause this behaviour:

• Route Checker [UPDATE] The GreasyFork version has just been updated
• Toolbox [UPDATE] New version released
• Simplify Place Geometry
• Quick HN [UPDATE] This script has been updated
• Panel Swap [UPDATE] No update yet, but there are manual fixes on the script's topic

Obviously this is not a bug/problem with the new release. But I'm posting here to warn people that these scripts (at least) are causing problems. I suggest you post on the relevant script threads.

Other scripts known to have problems

• WME FixUI [UPDATE] New version released
• WME Speedhelper (see above)

I'll try to keep an eye on this topic and add to the list as necessary.

Proffa71 wrote:Another thing this update caused is that the feature of panning the map with keyboard came literally impossible to use. Before: 5 * down arrow meant moving the screen's worth on map on my resolution. Now the same move takes 30+...

Moving one screen at a time with the numeric keypad is a function of WME Toolbox - nothing to do with native WME.

It isn't just Toolbox. Each one of the 5 listed above causes this problem.

Proffa71 wrote:

iainhouse wrote:

Proffa71 wrote:Another thing this update caused is that the feature of panning the map with keyboard came literally impossible to use. Before: 5 * down arrow meant moving the screen's worth on map on my resolution. Now the same move takes 30+...

Moving one screen at a time with the numeric keypad is a function of WME Toolbox - nothing to do with native WME.

I'm not talking about moving one screen at a time with the numeric keypad. I'm talking about panning map with arrow keys. I think it has to be WME native feature because it works on clean just installed browser without any add-ons on first time opening editor with it, just tested. The number of key strokes needed just got multiplied by 6 or something like it.

Sorry, I misunderstood you. You did mention "moving the screen's worth", so I thought you were refereeing to the Toolbox function that moves a whole screen width/height.

I confirm what you are reporting. Formerly, it took 6 key presses of left/right arrows to move one screens-worth horizontally. Now it takes 64 presses. Similarly, vertical movement of one screen originally took 4 presses - now it takes 37. (At my screen size, anyway).

It's doing this in Beta as well, so I can report it as a bug there, where it should get some attention.

atrophicshiner wrote:

delilush wrote:* Added new scrolling acceleration

Why Now I must ensure I stop my finger on laptop trackpad fully before releasing the mouse button, otherwise the map flings itself a ridiculous distance away from the area I was panning to

It seems quite popular with some people - though I admit I haven't tried it with a touchpad. "Disable kinetic panning" will be an option in WME FixUI shortly.

atrophicshiner wrote:Also why are all the categories now CAPITALISED It is difficult to read words that are all caps, another example of bad usability design

You're right that it's an example of bad usability design. It's also been that way since the new version of WME came out - and it's entirely deliberate by HQ. The CSS for this element includes "text-transform: uppercase" to force those words to upper case. Which is why WME FixUI overrides that setting. If you're just seeing them appear in upper case now, it may be that WME FixUI is off or the option is off - you need to enable some level of contrast enhancement for my override to take effect.

I've had a chance to play around with the new accelerated/kinetic panning. The effects can be massively magnified when using a touchpad.

Waze HQ please take note. I have little doubt that this feature was developed & tested by devs working at desks with mice/trackballs. As such, it's a potentially useful addition to WME. But had you tested it with the real user situation of a vast number of editors - a personal laptop being used in the home - you might have thought more carefully about it.

I'm not saying it's a bad feature, or that it should be removed again. But users should be given a choice. There's a native WME settings tab which is mostly empty space. Now I know you guys like empty space, but there's plenty of room in there for a user setting.

In the meantime, for those editors reading this who are already being driven crazy by it - WME FixUI now has an option to disable it.

Hint to dev team - that added a dozen lines to my code - including the UI and loading/saving/options.

AlObaili wrote:I noticed the panning acceleration effect becomes particularly annoying when the cursor leaves the map view area. The map keeps panning with the same acceleration right after when the cursor leaves the map view area.

e.g. try panning the map by holding your click and moving the cursor to the left very fast. As soon as the cursor leaves the map view area and enter the side panel the map will continue accelerating fast. I crossed the country boarders because of this

I think the panning should stop immediately if the cursor leaves the map view area.

It's actually part of the idea behind "kinetic movement" - if you're panning the map and you "hit the edge", the map will keep on panning instead of stopping abruptly, so it's intended to work like that.

In any case, I suspect it may not be possible to stop it happening. On my limited interaction with the feature's internals, I got the impression that it's a built-in feature of the OpenLayers framework, rather than anything added by Waze. They presumably noticed kinetic panning was available and decided to turn it on. Looking at the parameters controlling it, things like speed and deceleration can be controlled, but probably not preventing the panning continuing when you hit the edge.

atrophicshiner wrote:Not sure how long this has existed or if it is normal behaviour...

When selecting 2 segments that are identical except for the State in the name being different the left-hand panel refuses to show any information at all Normally when names differ the left-hand panel displays all info but adds No common name and Multiple for attributes.

This is a minor hinderance when closures span State borders.

It's a reported & confirmed bug.