Modify

Opened 3 years ago

Closed 2 years ago

Last modified 2 years ago

#5609 closed defect (fixed)

Unable to move node under another one

Reported by: Nakor Owned by: Nakor
Priority: major Component: Core
Version: Keywords:
Cc:

Description

Actual result:
node 0 is dragged

Expected result:
node 976570758 should be dragged

Works fin in 3641, broken in 3644

Attachments (1)

NavigatableComponent.java.patch (1.1 KB) - added by cmuelle8 3 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 Changed 3 years ago by bastiK

  • Owner changed from team to cmuelle8

Problem is for every unglue action (at a T junction).

Changed 3 years ago by cmuelle8

comment:2 Changed 3 years ago by bastiK

  • Resolution set to fixed
  • Status changed from new to closed

In [3652/josm]:

fixed #5609 (patch by cmuelle8) - Unable to move node under another one

comment:3 Changed 2 years ago by Nakor

  • Resolution fixed deleted
  • Status changed from closed to reopened

This is happening again. I am using 4092 at the moment.

comment:4 Changed 2 years ago by stoecker

  • Owner changed from cmuelle8 to Nakor
  • Status changed from reopened to 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 Changed 2 years ago by skyper

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.

Last edited 2 years ago by skyper (previous) (diff)

comment:6 Changed 2 years ago by Nakor

  • Resolution set to fixed
  • Status changed from needinfo to 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 Changed 2 years ago by stoecker

The selection sensitivity can be changed in advanced prefs (searching for snap?), but I think defaults are best for most users.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed .
as The resolution will be set. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.