#5609 closed defect (fixed)
Unable to move node under another one
Reported by: | Nakor | Owned by: | Nakor |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Core | Version: | |
Keywords: | Cc: |
Description
- Download area http://www.openstreetmap.org/?lat=42.57775&lon=-83.08886&zoom=16
- Select node 976570758
- Unglue it
- Select node 976570758 again
- Try to drag it
Actual result:
node 0 is dragged
Expected result:
node 976570758 should be dragged
Works fin in 3641, broken in 3644
Attachments (1)
Change History (8)
comment:1 by , 14 years ago
Owner: | changed from | to
---|
by , 14 years ago
Attachment: | NavigatableComponent.java.patch added |
---|
comment:3 by , 14 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
This is happening again. I am using 4092 at the moment.
comment:4 by , 14 years ago
Owner: | changed from | to
---|---|
Status: | reopened → needinfo |
Tested it. 4 nodes on top of each other. Cycling with middle click as well as selecting in selection list and folowing move works as expected. What does not work?
comment:5 by , 14 years ago
Let me get this right. The function is written to create a new node (id:0) and select it. Every other behaviour is a bug. Sorry wrong ticket.
I also can not reproduce any false behaviour and if you read the description carefully I get to the conclusion that this ticket is just invalid. Was me misreading.
My issues where either the other way around (id:0 selected and id:* moved) and happend right after unglue.
Mayby it has to to with layers or plugins. Had some strange moving of nodes in non-active layers but I think I blaime the turnlanes plugin for that, so far, as I can not really reproduce it right now.
comment:6 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | needinfo → closed |
I look a little bit more into it and in my case the nodes were slightly off one of each other. Clickink too much on the left would always select the same node, clicking one the right would always select the other node. Clickink right in the middle would keep the selection. So this is more "user error" combined with a very sensitive selection process.
comment:7 by , 14 years ago
The selection sensitivity can be changed in advanced prefs (searching for snap?), but I think defaults are best for most users.
Problem is for every unglue action (at a T junction).