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

Appearance settings

Commit 916445c

Browse filesBrowse files
committed
DOC: add deprecation note
1 parent 24f2b3e commit 916445c
Copy full SHA for 916445c

File tree

1 file changed

+20
-0
lines changed
Filter options

1 file changed

+20
-0
lines changed
+20Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
Make ``draw_idle`` method on ``FigureCanvasBase`` a no-op if not in interactive mode
2+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3+
4+
For backends that do not have an event loop associated with them
5+
(e.g. non-GUI backends) the semantics of `.FigureCanvasBase.draw_idle` are
6+
not clear. Previously it was equivalent to a non-re-entrant
7+
``fig.canvas.draw()`` call in all cases. Now it will be a no-op
8+
unless Matplotlib is in "interactive mode" (as given by
9+
`matplotlib.is_interactive`).
10+
11+
There are a number of derived properties in the Figure that we defer
12+
computing until draw time (limits, ticks, the size of things in screen
13+
space, optimized layout, etc). If you need to be sure that these
14+
values are correct (with any backend) call ::
15+
16+
fig.canvas.draw()
17+
18+
to force the Figure to fully render. This may break user code if it
19+
is relying on `pyplot.draw` (which internally calls ``draw_idle``)
20+
for the same effect in non-interactive mode.

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.