Run view port jobs afterwards (Fixes #2395) #2396
Merged
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.
notifyDataSetChanged()
may actually mutate some of the view port properties — stomping all over what the view port jobs just accomplished.This behavior is apparent when calling
moveViewToX()
on the chart view that has no frame yet. Prior to this change, callingmoveViewToX()
had no affect on a chart a chart that has no frame. That's because once the chart view was assigned a frame,notifyDataSetChanged()
call would actually mutate the view port's properties stomping all over what the view port jobs just finished doing.