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
This state transition only happens when the InteractionTracker is in the Idle state and TryUpdatePositionWithVelocity or TryUpdateScaleWithVelocity is called.
Just scrolling with mouse wheel will cause Idle → Inertia transition. There are no TryUpdatePositionWithVelocity calls involved.
Also, the method name is TryUpdatePositionWithAdditionalVelocity, so that's a typo as well.
NOTE: When Idle transitions to Inertia with mouse wheel, the request id is always zero, indicating that it doesn't involve TryUpdatePositionWithAdditionalVelocity. Because:
Returns the request ID. On state transitions, the request which caused the change in state will be included in the args. These IDs will start at 1 and increase with each try call during the lifetime of the application.
The text was updated successfully, but these errors were encountered:
Page: https://learn.microsoft.com/en-us/windows/windows-app-sdk/api/winrt/microsoft.ui.composition.interactions.interactiontracker?view=windows-app-sdk-1.3
The Idle → Inertia transition doc says:
However, given:
Just scrolling with mouse wheel will cause Idle → Inertia transition. There are no
TryUpdatePositionWithVelocity
calls involved.Also, the method name is
TryUpdatePositionWithAdditionalVelocity
, so that's a typo as well.NOTE: When Idle transitions to Inertia with mouse wheel, the request id is always zero, indicating that it doesn't involve
TryUpdatePositionWithAdditionalVelocity
. Because:https://learn.microsoft.com/en-us/windows/windows-app-sdk/api/winrt/microsoft.ui.composition.interactions.interactiontracker.tryupdatepositionwithadditionalvelocity?view=windows-app-sdk-1.4
The text was updated successfully, but these errors were encountered: