Skip to content

Conversation

@benmccann
Copy link
Contributor

Closes #6715

This improves memory usage by not keeping around an old copy of the ticks from before autoSkip is run and also improves performance because when we iterate over all ticks that's now a much smaller set

@benmccann benmccann force-pushed the rm-ticksToDraw branch 2 times, most recently from 5ee0234 to 675a031 Compare November 11, 2019 04:58
@kurkle
Copy link
Member

kurkle commented Nov 11, 2019

'auto' mode does not offset anymore?

@benmccann
Copy link
Contributor Author

It still does, but it's calculated before autoSkipping happens, and I'm not sure how to test what amount of offset should have been generated after the autoSkipping occurs

Copy link
Member

@kurkle kurkle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amount of offset added might change, but lets deal with that later if it becomes an issue.

@etimberg etimberg merged commit cb95a36 into chartjs:master Nov 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

getPixelForTick is confusing and possibly inconsistent

3 participants