Is there any way to enable the predictable 'click & drag' scrolling? The default speed is way too sensitive for any useful work....

[EDIT] Never mind. I disabled all scripts, cleared cache and had another look. It looks like one or other script was fiddling or clashing with mouse-down events. I see the default is still click & drag.

The behavior that I saw was that when I left-clicked, the window would start scrolling and the speed was dependent on how far the mouse was moved, pretty much like one of the joysticks you find standard on notebooks these days.

Glad to see this is not how I thought it was.

Now to update scripts & find the culprit, if it's still there....

Last edited by Kuhlkatz on Mon Nov 05, 2012 5:16 pm, edited 1 time in total.

skbun wrote:Agh, I realize how this might have sounded now, as you were the one who wrote that portion of the Wiki! Trust me when I say, sorry!

I agree wholeheartedly with you that primary and alt must match is the way to go. I'm pointing out the details to Waze so it could be fixed, because this mismatch problem can be really hard to find with our existing tools, and it -does- cause real problems we have to edit out.

I wasn't taking any offense at this, be assured! I requested that they develop the editor to enforce this as it's really the only way that makes sense. What makes even less sense with the current implementation, is that if the road is a highway or freeway type, they default the city to None.

skbun wrote:An alternate name street must also have the same city as the primary segment. (My emphasis added)

This may be a best practice, but it's not enforced by WME. Here's some bullet points of what's possible.

Yes, there are lots of things which we have as guidelines/best practices which the editor does not enforce. This is one of them.

Agh, I realize how this might have sounded now, as you were the one who wrote that portion of the Wiki! Trust me when I say, sorry!

I agree wholeheartedly with you that primary and alt must match is the way to go. I'm pointing out the details to Waze so it could be fixed, because this mismatch problem can be really hard to find with our existing tools, and it -does- cause real problems we have to edit out.

I'm pretty sure, to Waze, It wouldn't really be that hard, either. At 'Apply' time on the Edit Segment dialog, force the CityID of any alt name to be the same as the primary, regardless of what the user did in the meantime. Simple as that?