Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit e509e40

Browse files
authored
Merge pull request #24551 from meeseeksmachine/auto-backport-of-pr-24548-on-v3.6.x
Backport PR #24548 on branch v3.6.x (DOC: improved the doc for layout_engine.py)
2 parents 787843c + 93a6d45 commit e509e40

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

lib/matplotlib/layout_engine.py

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,10 @@
55
`~.LayoutEngine` defined here (or *None* for no layout). At draw time
66
``figure.get_layout_engine().execute()`` is called, the goal of which is
77
usually to rearrange Axes on the figure to produce a pleasing layout. This is
8-
like a ``draw`` callback, however when printing we disable the layout engine
9-
for the final draw and it is useful to know the layout engine while the figure
10-
is being created, in particular to deal with colorbars.
8+
like a ``draw`` callback but with two differences. First, when printing we
9+
disable the layout engine for the final draw. Second, it is useful to know the
10+
layout engine while the figure is being created. In particular, colorbars are
11+
made differently with different layout engines (for historical reasons).
1112
1213
Matplotlib supplies two layout engines, `.TightLayoutEngine` and
1314
`.ConstrainedLayoutEngine`. Third parties can create their own layout engine

0 commit comments

Comments
 (0)