Skip to content

Commit 782750e

Browse files
timhoffmtacaswell
andauthored
Reword what's new message
Co-authored-by: Thomas A Caswell <[email protected]>
1 parent 1784c73 commit 782750e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/users/next_whats_new/pyplot-register-figure.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,8 +48,8 @@ Technical detail: Standalone figures use `.FigureCanvasBase` as canvas. This is
4848
replaced by a backend-dependent subclass when registering with pyplot, and is
4949
reset to `.FigureCanvasBase` when the figure is closed. `.Figure.savefig` uses
5050
the current canvas to save the figure (if possible). Since `.FigureCanvasBase`
51-
is Agg-based any Agg-based backend will create the same file output. There may
52-
be slight differences for non-Agg backends; e.g. if you use "GTK4Cairo" as
51+
can not render the figure, when using save fig it will fallback to `.FigureCanvasAgg` which is Agg-based. Any Agg-based backend will create the same file output, however
52+
There may be slight differences for non-Agg backends; e.g. if you use "GTK4Cairo" as
5353
interactive backend, ``fig.savefig("file.png")`` may create a slightly different
5454
image depending on whether the figure is registered with pyplot or not. In
5555
general, you should not store a reference to the canvas, but rather always

0 commit comments

Comments
 (0)