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
A common operation when modifying the geometry of a way is to drag multiple nodes in succession. In iD, you can do this without having to re-select the way after dragging a node. In Rapid, after dragging a node in a way, you need to re-select the way before you can drag another node, making this operation less efficient.
Version
2.00-alpha.3.3
What browser are you seeing the problem on? What version are you running?
Chrome v109.0
Steps to reproduce
Select a way
Drag a node
The browser URL at the time you encountered the bug
(re: #771, #760)
This was addressed quickly in earlier commits, but I think this handles the issue
in a better way.
If the node being dragged has a parent that is already selected, then we preserve
the selection (lines or areas), otherwise we select the node.
Description
A common operation when modifying the geometry of a way is to drag multiple nodes in succession. In iD, you can do this without having to re-select the way after dragging a node. In Rapid, after dragging a node in a way, you need to re-select the way before you can drag another node, making this operation less efficient.
Version
2.00-alpha.3.3
What browser are you seeing the problem on? What version are you running?
Chrome v109.0
Steps to reproduce
The browser URL at the time you encountered the bug
https://mapwith.ai/rapid-v2-alpha3#background=Bing&datasets=fbRoads,msBuildings&disable_features=boundaries&map=21.58/40.78602/-111.92437
The text was updated successfully, but these errors were encountered: