Open
Conversation
… I thank catherine for the inspiration with the fixedrange, and now it is just autorange instead of fixed range.
1catherinem
referenced
this pull request
Nov 13, 2025
fixedrange=TRUE makes it so that the X-axis cannot be expanded past its defined range (I.e. go to -1), and so the user cannot pan/zoom to an undefined part of the range.
1catherinem
added a commit
to 1catherinem/ORCID-Data-Visualization
that referenced
this pull request
Nov 13, 2025
I changed this so that if pull request crkn-rcdr#39 is merged into main, my pull request will not conflict.
Not all of these changes should be merged. I could not stage only some things. Some comments are in french now
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
1 participant
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.
Forcing autoscale removes the -1 (as there are not -1 datapoints to pull from). This builds on the solution of fixedrange=TRUE as suggested by Catherine. Except, it does not force the user to lock into a specific view. This means that maybe we need to have another discussion about whether or not that is something we want.
But the issue I originally brought up is solved, it would seem.