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 documentation of interact_pointer_pos says:
"Where the pointer (mouse/touch) were when this widget was clicked or dragged."
I interpret that as the start point of the dragging/click. However, it seems like it is the current position of the mouse.
Ideally (for me), it should be as described as I need to get the exact start position of a drag and, since, it requires a bit of dragging to determine that drag happens, I think that corresponds to return press_origin?
If it behaves as expected, one should probably rephrase the documentation.
I believe the behavior is working as intended, and the usecase is to get the position of the tap in touch events. Since the click is triggered when the finger is lifted and lifting triggers a PointerGone event, hover_pos would be None during the click frame, and interact_pointer_pos is still Some (remembering the position from the last frame).
I get that the wording is confusing though, that could definitely be improved.
Describe the bug
The documentation of
interact_pointer_pos
says:"Where the pointer (mouse/touch) were when this widget was clicked or dragged."
I interpret that as the start point of the dragging/click. However, it seems like it is the current position of the mouse.
Ideally (for me), it should be as described as I need to get the exact start position of a drag and, since, it requires a bit of dragging to determine that drag happens, I think that corresponds to return
press_origin
?If it behaves as expected, one should probably rephrase the documentation.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The value should not change (if the doc is correct).
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: