Changes between Initial Version and Version 1 of Ticket #18420, comment 3


Ignore:
Timestamp:
2019-12-21T10:36:45+01:00 (5 months ago)
Author:
GerdP
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18420, comment 3

    initial v1  
    11Replying to [comment:2 Don-vip]:
    22> Could it be a regression of r15428?
    3 Hard to say without an example. The results depend on the distance and the zoom and the resolution of the screen.
    4 Load attached example and select the single node. On my PC I see this
     3Hard to say without an example. The results depend on the distance and the zoom and the resolution of the screen and a preference setting.
     4Load attached example and select the single node. On my PC (1920x1080 screen resolution) I see this
    55Case 1 Press 3 (zoom to selection) followed by n: Nothing happens
    66Case 2: Press - (zoom out) followed by n: Node is joined to the closest building
     
    88Case 4: undo, 3, zoom out 4 or more times, n : Popup saying that there are multiple target ways
    99
    10 I think Case 1 is the problem here. Reason for the behaviour is that the action selects way segments within a fixed range of screen pixels using `NavigatableComponent.getNearestWaySegmentsImpl()`. The range value is stored in preference mappaint.segment.snap-distance, default is 10.
     10I think Case 1 is the problem here. Reason for the behaviour is that the action selects way segments within a fixed range of screen pixels using `NavigatableComponent.getNearestWaySegmentsImpl()`. The range value is stored in preference `mappaint.segment.snap-distance`, default is 10, for screens with a high resoltion this might be too small.
    1111