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: StellanL [Submitted to the original trac issue database at 11.25pm, Sunday, 12th December 2010]
It gets deselected as soon as you release the mouse button. In P1, you can drag the map with a way selected. This is very useful, i.e. when you are following a way to see what it connects to.
The text was updated successfully, but these errors were encountered:
Author: stevage [Added to the original trac issue at 12.52pm, Tuesday, 14th December 2010]
Fixed (I think) in 24745.
Revision: 24745
Author: stevage
Date: 11:49:59 PM, Tuesday, 14 December 2010
Message:
Fix bug: #3391: Dragging map deselects current way
Mouse up was causing both CLICK and MOUSE_UP events. Like someone else who commented in the source code, Idon't know what's going on, but this fix will presumably allow correct behaviour for both SelectedMarker and SelectedWay states.
Reporter: StellanL
[Submitted to the original trac issue database at 11.25pm, Sunday, 12th December 2010]
It gets deselected as soon as you release the mouse button. In P1, you can drag the map with a way selected. This is very useful, i.e. when you are following a way to see what it connects to.
The text was updated successfully, but these errors were encountered: