Fix initial padding and startPosition when scrolling is delayed #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When you add a
startPadding
and use thestartAfter
to delay the scrolling after 'n' seconds: on this few 'n' seconds thestartPadding
is not applied (internally, thestartPosition
is not correctly set).Below, on the first 5 seconds, you can see that the
startPadding
is ignored, and cause a "jump" effect when it starts scrolling:This fix here ensures that the
startPosition
is correctly set from theinitState
of this Widget.