-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Automargin fixes #2681
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Automargin fixes #2681
Changes from 1 commit
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
970db80
stop mutating user data to add uids
alexcjohnson 26278de
some test cleanup
alexcjohnson 6dd68bd
first cut at updating automargin logic
alexcjohnson fa86147
refactor colorbars for simpler connection to trace attributes
alexcjohnson 95f9b33
test legend, rangeselector, rangeslider automargin updates
alexcjohnson 8f3da82
provide uids to traces a little earlier - to fix carpet clip ids
alexcjohnson f9fbbc6
:hocho: colorbar.vals - seems like that was all obsolete anyway
alexcjohnson 222f396
cleanup in sliders_test
alexcjohnson bd07df7
simplify inner plot size tests with custom_assertions
alexcjohnson 84a5695
fix and test slider x positioning when they push margins
alexcjohnson 3deab4c
move sliders to the updated automargin framework
alexcjohnson bb6c720
use bg rect instead of grids for assertPlotSize
alexcjohnson d02c76b
base fractional colorbar size on post-expanded-margin plot size
alexcjohnson 5d31324
comment and fix on assertPlotSize with margin.pad
alexcjohnson 16ea22a
reduce automargin padding for small explicit margins
alexcjohnson 24aeb7c
axRange edits don't need drawMarginPushers after all
alexcjohnson 230a782
automargin comment updates
alexcjohnson File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mentioned this in the commit message:
but for more detail: colorbars (and possibly a few others?) when sized as plot fraction they use the initial margins to convert plot fraction to pixels - meaning that if the margins expand beyond that, a colorbar with length "1" would actually be taller than the plot area. This is probably fine if it's the colorbar itself that's expanding the margin - that means it's off-center and thus not aligned with the plot, so who really cares if it's a little bigger than the plot? But if something else (eg a rangeslider, or axis labels) expanded the margin, all of a sudden the colorbar is misaligned. Using
yt/yb
we can size it correctly without getting into an infinite loop of automargin calls. Actually now that I think of the case ^^ which would be pretty ugly, I may try to do that in this PR as well.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the info 📚