useUpdateNodeInternals doesn't update handle positions during active connection about xyflow

[moklick]

Yep, that's not possible. We store the handles in a lookup when the connection starts and won't update it during an ongoing connection. Maybe you could separate the displayed handle from the real one? The real handle always stays at the same position but only the visible / non-interactive one changes its position?

[DenizUgur]

I get what you're saying, I would also need to increase the hover trigger area to compensate for that delay then. All of it seems a bit hacky though. May I ask the reasoning behind this? As source handles behave correctly in this case.

If it's also a won't fix situation, could you tell me where is the related logic located so that I can fork or monkey patch it?

[DenizUgur]

Okay it appears that this comes from the following snippet. I get why you are using a lookup here but if there is a way to know when updateNodeInternals is called then this lookup should be invalidated. I've tested it and updating the lookup here solves this issue. I'll investigate the code a little more to see how I can get notified about this and open a PR about it.

xyflow/packages/system/src/xyhandle/XYHandle.ts

Lines 151 to 161 in 82f40b4

	function onPointerMove(event: MouseEvent | TouchEvent) {
	const transform = getTransform();
	connectionPosition = getEventPosition(event, containerBounds);
	closestHandle = getClosestHandle(
	pointToRendererPoint(connectionPosition, transform, false, [1, 1]),
	connectionRadius,
	handleLookup
	);
	if (!autoPanStarted) {
	autoPan();