Merged
Conversation
- Use extend so visibleAxes remains a flat list. - More robust logic for detecting adding an AxisItem instance to mulitple plots and suggest a workaround in the error message.
Member
|
Nice fix @ixjlyons Merging. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 #1358
I believe this is the intention of the logic that's there currently. Technically, it does appear to be possible to use a single
AxisItemfor multiplePlotItems, but the conditions under which this works (and doesn't cause a segfault) aren't crystal clear to me. In the future, if someone figures out how to robustly detect when it's ok to do so, we can allow for it. For now this should make things work as intended and I'm pretty sure separate linked instances should work equivalently.