-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Sticky margins #7476
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
Sticky margins #7476
Changes from 1 commit
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
b73a939
Minor cleanups.
anntzer a2e35cc
Sticky margins cancellation system.
anntzer 0fa187e
Sticky margins support for contour.
anntzer e646152
Update test images.
anntzer 5d82bcb
DOC: remove docs for removed API
tacaswell 16cba9d
FIX: use valid local variable
tacaswell eb1ce75
DOC: remove margin from docs
tacaswell 1285264
Set hist minimum value to 0
efiring 253eac3
fix sticky-handling of 0 with log scale
efiring fbf97d4
Rely on normal autoscaling for stepfilled hist.
efiring 5f942c8
hist: correct minimum stickies for log case; remove unneeded code
efiring 36fcfe5
change stickies to sticky_edges; clarify edge calculation in contour
efiring 70a37f1
fix sticky-handling in raw ContourSet; remove tight specifications
efiring 1a50dda
restore autoscale(tight=True); still needed for classic mode.
efiring 717c278
minor code rearrangement for clarity; augmented sticky_edges docstring
efiring 840986e
test_triangulation: increase tolerance on Windows
efiring 1a86b08
DOC sticky edges now uses numpydoc
NelleV 04298b8
add ax.use_sticky_edges property
efiring 93c1bd8
MNT: remove extraneous autoscale call
tacaswell 360dba7
Remove extraneous stale setting; fix indent.
anntzer 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
Prev
Previous commit
Remove extraneous stale setting; fix indent.
- Loading branch information
commit 360dba71f6f3518ed6ed1e360a312bcd6fa06cec
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
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.
Should this also re-trigger an auto-scaling?
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 was wondering about that also, but decided against it. I could be convinced otherwise for now, but long term I think we might want to consolidate the autoscaling at draw time instead of having calls to
autoscale_view
sprinkled all over the place. I don't think it makes sense to trigger autoscaling with every change in the state of the plot.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 am convinced
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.
Do we actually need the axes as stale? This won't have an effect until the next autoscaling, which should also mark it as stale, right?
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.
Good point. You are welcome to replace it with a comment to that effect. I think I put the call in because we tend to have it in every function that potentially changes how the plot will look.
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.
Done, together with indentation fix below.
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.
Not sure I agree with this, if as Eric suggests above we move towards autoscaling a draw time (as late as possible) then marking the figure as stale will trigger a re-draw (and hence the re-autoscaling).
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.
Good point.
On the other hand this is easy enough to revert when we do switch to draw-time autoscaling (which makes complete sense).