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 Clay_OnHover callback does not receive the CLAY_POINTER_DATA_RELEASED_THIS_FRAME event when the pointer state is updated as follows:
// (in the main loop, before layouting and rendering)if (isTouching)
{
Clay_SetPointerState((Clay_Vector2){touch.px, touch.py}, true);
}
else
{
Clay_SetPointerState((Clay_Vector2){-1, -1}, false);
}
This behavior occurs in my use case with touchscreen input, where I only provide the pointer position when the screen is being touched.
STEPS TO REPRODUCE THE ISSUE:
When isPointerDown changes to false and position is updated to { -1, -1 }, the Clay_OnHover callback does not receive the CLAY_POINTER_DATA_RELEASED_THIS_FRAME pointer state.
However, if I cache the previous touch position and pass that togheter with the isPointerDown update to false, Clay_OnHover receives the correct pointer state update.
The text was updated successfully, but these errors were encountered:
The
Clay_OnHover
callback does not receive theCLAY_POINTER_DATA_RELEASED_THIS_FRAME
event when the pointer state is updated as follows:This behavior occurs in my use case with touchscreen input, where I only provide the pointer position when the screen is being touched.
STEPS TO REPRODUCE THE ISSUE:
When isPointerDown changes to
false
and position is updated to{ -1, -1 }
, the Clay_OnHover callback does not receive the CLAY_POINTER_DATA_RELEASED_THIS_FRAME pointer state.However, if I cache the previous touch position and pass that togheter with the
isPointerDown
update tofalse
,Clay_OnHover
receives the correct pointer state update.The text was updated successfully, but these errors were encountered: