Move Node onto Way more difficult at high zoom

[A_Pirard]

At high zoom, function "Move Node onto Way" (N key) requires that the node be excessively near the way.
And BTW, function "Merge Nodes" (M key) has the same excessive proximity requirement; maybe same problem.
Both should work at even a large distance if there is no confusion with another way or node.

May I be off topic very shortly with asking a technical advice?
Would I sound idiot by suggesting that a tool could invoke another tool?
Is it possible?
Best is to explain the specifics if you don't tell everybody.
It's about AreaSelector.
I would like it to invoke Replace Geometry of a being replaced object.
Only problem I think is returning to AS environment, but AS can do it. EDIT: off-topic

[A_Pirard]

Update: I'm not sure about "since 14178" after all.
What I'm sure of is that when I use AreaSelect to create a new house, that AS should put some nodes on (merge with) ways or nodes of the next house but does not, then I must drag those nodes extremely near these to be able to use N or M.
Hence the request is to do it over "a large distance".

TIA.

[Don-vip]

Please provide a sample file showing the problem. Thanks.

[A_Pirard]

Hi, thanks,

The layer is BE SPW PICC.
It's about correcting AreaSelector imprecision.
Hence, I'm working at high zooms.
This is speed tagging (1 house/~10 sec complete if no touch up is needed).
I just noticed that the inconvenience occurs above some zoom level.
In N25.OSM, the 2 north corners of south house cannot be N'ed to the way at zoom ≥25.
In M24.OSM the NW corner of south house cannot be M'ed to nearby node at zoom ≥24.
Unless time is spent to select both nodes, of course.
So, either the nodes have to be moved or zoom must constantly change: time loss.
Maybe also other node "gluing" functions that I don't use often.
Not sure why I feel this as a new inconvenience.
A higher maximum distance distance would be welcome. Maybe it was before.
Or depending on zoom.
TIA.

[Don-vip]

I can reproduce the problem for N with file N25.osm but not with M with file M24.osm. At maximum zoom level I'm still able to merge the nodes.

[A_Pirard]

Hi Don,

You probably select the two nodes. I wrote I select only one because
1) of speed : alternating way/node selections twice dozens of times takes time
2) selecting a single one makes sure which node is moving

Thanks for looking into this issue.
TIA.

[Don-vip]

OK I didn't even know we could merge nodes by selecting only on of them. I confirm I can reproduce both problems now.