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
If we check the code we can see that canReachTargetWithDecay will always be false and the reason is if targetOffsetX is greater than actualTargetX (which either be 0 or drawerWidth) then targetDifference will always in negative (<0) but in the first condition of last check targetDifference > 0f which always be <0 hence the result will be false and same goes for the second condition if targetOffsetX is smaller then targetDifference will always >0f (positive) hence second condition will always be false.
Because of this, the running conditions of different animation methods will also be not required
Is there an existing issue for this?
Is there a StackOverflow question about this issue?
Is this an issue related to one of the samples?
Sample app
Other (bug not related to sample app)
What happened?
In Jetlagged we have JetLaggedDrawer.kt
If we check the code we can see that
canReachTargetWithDecay
will always be false and the reason is iftargetOffsetX
is greater thanactualTargetX
(which either be 0 or drawerWidth) thentargetDifference
will always in negative (<0) but in the first condition of last checktargetDifference > 0f
which always be <0 hence the result will be false and same goes for the second condition iftargetOffsetX
is smaller thentargetDifference
will always >0f (positive) hence second condition will always be false.Because of this, the running conditions of different animation methods will also be not required
I might be wrong here Please CMIMW @riggaroo
Related PR #1174
Relevant logcat output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: