Fix heatmapgl point number event data #1884
Merged
Conversation
This file contains hidden or 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
- so that z[ny][nx] where ny = pointNumber[1] and nx = pointNumber[0]
etpinard
commented
Jul 14, 2017
| textLabel: this.textLabels[index], | ||
| name: this.name, | ||
| pointIndex: [xIndex, yIndex], | ||
| pointIndex: [yIndex, xIndex], |
There was a problem hiding this comment.
thanks @dfcreative for that #1825 (comment)
|
Works for me! 💃 |
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.
fixes #1825
Luckily, the problem described in #1825 only concerns
heatmapgl- as opposed to the solution proposed in #1833.The patch is simple. It brings
heatmapgl'spointNumberevent data field on par with other 2D trace types. This PR also adds an asymmetricheatmapglhover test case.cc @alexcjohnson @dfcreative