You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Bug described here was first also described in this comment on a stackoverflow answer which suggests the use of MouseControlUtil.addSelectionRectangleGesture:
Whenever I call the function with the final Parent root argument being some Pane within a Scene, the rectangle position is incorrect:
The reason to me seems to be in the performDragBegin method, MouseControlUtil.java L385-L386
The initial position is obtained from the scene-absolute coordinates, but the rectangle is attached to an element down in the hierarchy of the scene tree - that does not seem correct and i suspect it is the cause of this problem.
Sidenote:
from the design of this peace of te code, it seems to be intended in a way, that the final Parent root argument is in fact - as in this example - down in the hierarchy of the scene tree.
I am aware that this is experimental code, so I am submitting this issue, so this can be fixed.
The text was updated successfully, but these errors were encountered:
The MouseControlUtil does only compute the scaling (LocalToSceneTransform) but it ignores the necessary translation. In VWorkflows we do the necessary translation: See lines 408 - 445.
The Bug described here was first also described in this comment on a stackoverflow answer which suggests the use of
MouseControlUtil.addSelectionRectangleGesture
:Whenever I call the function with the
final Parent root
argument being somePane
within a Scene, the rectangle position is incorrect:The reason to me seems to be in the performDragBegin method, MouseControlUtil.java L385-L386
The initial position is obtained from the scene-absolute coordinates, but the rectangle is attached to an element down in the hierarchy of the scene tree - that does not seem correct and i suspect it is the cause of this problem.
Sidenote:
from the design of this peace of te code, it seems to be intended in a way, that the
final Parent root
argument is in fact - as in this example - down in the hierarchy of the scene tree.I am aware that this is experimental code, so I am submitting this issue, so this can be fixed.
The text was updated successfully, but these errors were encountered: