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: tms13 [Submitted to the original trac issue database at 1.21pm, Thursday, 29th April 2010]
Sometimes, when editing a long way, it's easy to accidentally move the way instead of one of its nodes. Undoing this takes several minutes of maxed-out CPU if the way has more than a few hundred nodes. Either undo should be faster, or move mode should be lockable to moving nodes only when that's required.
The text was updated successfully, but these errors were encountered:
Reporter: tms13
[Submitted to the original trac issue database at 1.21pm, Thursday, 29th April 2010]
Sometimes, when editing a long way, it's easy to accidentally move the way instead of one of its nodes. Undoing this takes several minutes of maxed-out CPU if the way has more than a few hundred nodes. Either undo should be faster, or move mode should be lockable to moving nodes only when that's required.
The text was updated successfully, but these errors were encountered: