[Help]: Issue with connection reassignment #328
What are you trying to achieve?Hi! I've been trying Foblex Flow recently and got stuck implementing the following use case: The scenario:
As a result, "Connection 1" is grabbed instead of "Connection 2". However, what I'm trying to achieve is for "Connection 2" to be grabbed, just like shown in the image below:
Is there any way to achieve this behavior? What have you tried so far?I tried following the examples in the documentation but found nothing related to this specific issue. Relevant Example or Documentation Page (optional)No response Additional Context (optional)No response |
Replies: 1 comment
|
Good catch again 🙌 Confirmed and fixed. When several connections share a connector, their reassign handles coincide - and the grab went by registration order, ignoring which connection you selected. Now the selected connection wins the grab, so your exact scenario - select "Connection 2", drag its start handle - works like in your second screenshot. The fix lands in the next release 19.2.0 (together with the closest-connector drop resolution from #326). If you like where the library is going - a ⭐ on the repo helps a lot 🙌 |


Good catch again 🙌
Confirmed and fixed. When several connections share a connector, their reassign handles coincide - and the grab went by registration order, ignoring which connection you selected. Now the selected connection wins the grab, so your exact scenario - select "Connection 2", drag its start handle - works like in your second screenshot.
The fix lands in the next release 19.2.0 (together with the closest-connector drop resolution from #326).
If you like where the library is going - a ⭐ on the repo helps a lot 🙌