Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

selected element will not move always #5985

Closed
sun-geo opened this issue Feb 26, 2019 · 2 comments
Closed

selected element will not move always #5985

sun-geo opened this issue Feb 26, 2019 · 2 comments

Comments

@sun-geo
Copy link
Contributor

sun-geo commented Feb 26, 2019

Expected behavior

after disconnecting a shared* node with tag (e.g. highway=bus_stop) then the node of the selected element (either way or area) should also used for a potential move afterwards
*shared e.g. with way(highway=tertiary) and area(landuse=residential)

Actual behavior

sometimes the other element is moved (this behavior is annoying and persist for a long time - i was just too lazy to report it... )

steps to reproduce:
0. have two shared elements: e.g. way highway=tertiary (should also happened for highway=* ) and an area of e.g. landuse=residential (should also happened for landuse=* )
0. have a shared node on this structure with tag highway=bus_stop or highway=stop

  1. select a shared node (e.g. highway=bus_stop)
  2. right mouse click => disconnect
  3. select the area (landuse=residential)
  4. move the node (highway=bus_stop):
    => the node and line of area (landuse=residential) is modified: OK :-)
  5. combine the nodes (highway=bus_stop) of way and area
  6. select a shared node (e.g. highway=bus_stop)
  7. right mouse click => disconnect
  8. select the area (landuse=residential)
  9. move the node (highway=bus_stop):
    => the node and line of way (highway=tertiary) is modified: not OK :-(

Screenshots illustrating the current situation

by using the preview.editor.com:
move selected5

@sun-geo
Copy link
Contributor Author

sun-geo commented Feb 26, 2019

ps: please correct/change the issue subject title text for better understanding

@bhousel
Copy link
Member

bhousel commented Feb 26, 2019

This is #2206

@bhousel bhousel closed this as completed Feb 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants