You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: Mueck [Submitted to the original trac issue database at 8.39pm, Tuesday, 2nd September 2008]
Holding left mouse button while moving the mouse moves around the map.
well...
If you do this near by a selected way, it might be that you move the way by mistake instead of the map, because cursor is 1 pixel at the wrong place... Panic! Westminster is moved into the river Thames! ;-)
It might be useful to "protect" the ways from this mistake.
For moving the ways you should need: pressing left mouse button AND pressing the shift key and moving the mouse...
So it is clearly different from moving the map.
Moving a node instead of the map is also an error, but consequences are smaller, only one corner of Big Ben ...
The text was updated successfully, but these errors were encountered:
Author: StellanL [Added to the original trac issue at 8.08am, Sunday, 7th September 2008]
An alternative solution would be to add an option to enable/disable the "move way" function.
(I too have had a lot of problems accidentally moving whole coastlines instead of just one point on it. This (and the undo) often ties up my browser for minutes.)
Reporter: Mueck
[Submitted to the original trac issue database at 8.39pm, Tuesday, 2nd September 2008]
Holding left mouse button while moving the mouse moves around the map.
well...
If you do this near by a selected way, it might be that you move the way by mistake instead of the map, because cursor is 1 pixel at the wrong place... Panic! Westminster is moved into the river Thames! ;-)
It might be useful to "protect" the ways from this mistake.
For moving the ways you should need: pressing left mouse button AND pressing the shift key and moving the mouse...
So it is clearly different from moving the map.
Moving a node instead of the map is also an error, but consequences are smaller, only one corner of Big Ben ...
The text was updated successfully, but these errors were encountered: