02-20-2022, 06:22 AM
In a CustomWidget, a Mac user can drag in the control and the drag event keeps recording even after the user drags beyond the bounds of the control and the event correctly ends when the mouse button is released.
In Windows, the drag seems to end when the cursor goes beyond the control's bounds, but when the cursor hovers over the control again, the CustomWidget thinks the user is still dragging, even with the mouse up. The drag event can only be ended by clicking and initiating a mouseUp within the control's bounds.
A workaround I use exits the drag callback if a mouse button is not pressed, using hdi::core::mouseButtonsPressed(). Is there another approach for handling this Windows behavior?
In Windows, the drag seems to end when the cursor goes beyond the control's bounds, but when the cursor hovers over the control again, the CustomWidget thinks the user is still dragging, even with the mouse up. The drag event can only be ended by clicking and initiating a mouseUp within the control's bounds.
A workaround I use exits the drag callback if a mouse button is not pressed, using hdi::core::mouseButtonsPressed(). Is there another approach for handling this Windows behavior?