Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitfbfa28d

Browse files
authored
Merge pull request#24548 from ramvikrams/t2
DOC: improved the doc for layout_engine.py
2 parents4e059bc +3650122 commitfbfa28d

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)

[8]ページ先頭

©2009-2025 Movatter.jp