enhancing Curved Lines support: differentiating between "real" datapoints and interpolated spline points #123
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
enhancing Curved Lines support: differentiating between "real" datapoints and interpolated spline points (as described in #122, but defaulting to not display.
I would have built this into the original Curved Lines support if I'd have been able to figure out how. Because when using Curved Lines, much of the data is a guesstimate rather than from an actual data point, I wanted to be able to illustrate the difference in the tooltip. Rather than having the tooltip simply report on a made-up x and y value, this would at least notify the user which points are made up when the rekevabt option is set to true.