-
Notifications
You must be signed in to change notification settings - Fork 890
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
tight_layout
versus constrained_layout
#30
Comments
The reason is that I did not know about |
Simply speaking: Constrained layout does a better layouting job in many cases. From constrained layout guide:
But that's only the technical implementation. @jklymak I don't think we have an explanation what that means for the user. Would be nice to add a sentence to the constrained layout guide as well. |
constrained layout works with multi-axes colorbars, it makes axes match size whether they have colorbars or not, it works with nested gridspecs. It works with uneven subplot layouts (i.e. 2 axes in one column, and 3 axes in another column). It also works interactively - i.e. when the axes is resized, which I don't think tight_layout does. Overall, I think most users want constrained_layout versus tight_layout - I'm not aware of situations where tight_layout is better, but happy for reports. |
And is possible to remove white margins in the process? (like |
Sure if you set hpad and wpad to zero. |
cheatsheets/handout-tips.tex
Line 215 in 329e0ba
tight_layout
in particular. Is there a reason to not also call outconstrained_layout
? In generalconstrained_layout
is more "automatic".The text was updated successfully, but these errors were encountered: