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
Not sure if this is due to a new version of watchOS, but PageScrollState.swift's line 70: self.pageOffset = 0.0
seems to reset the position of the "previous" page to its origin before doing the animation to the new page.
As a result, the swipe to an adjacent page has sort of a hiccup.
Moving the statement inside the DispatchQueue.main.async block fixes the issue. Lines 69~76 would change as follows:
Even so, swipe "end animations" still do seem a little unnatural, probably because the remaining distance--whatever it might be--is always reached in 0.2 second in an .easeInOut animation, which might benefit from being .easeOut only.
Thank you.
The text was updated successfully, but these errors were encountered:
Not sure if this is due to a new version of watchOS, but
PageScrollState.swift
's line 70:self.pageOffset = 0.0
seems to reset the position of the "previous" page to its origin before doing the animation to the new page.
As a result, the swipe to an adjacent page has sort of a hiccup.
Moving the statement inside the
DispatchQueue.main.async
block fixes the issue. Lines 69~76 would change as follows:Even so, swipe "end animations" still do seem a little unnatural, probably because the remaining distance--whatever it might be--is always reached in 0.2 second in an
.easeInOut
animation, which might benefit from being.easeOut
only.Thank you.
The text was updated successfully, but these errors were encountered: