You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FigureCanvasWebAgg and FigureCanvasNbAgg empty subclasses of
FigureCanvasWebAggCore. They only differed in that WebAggCore did not
define the (common) timer class, which is easily fixed (but the
TimerTornado definition needs to be moved above the
FigureCanvasWegAggCore definition), and that WebAgg explicitly redefined
`show` to use the module's `show`, whereas WebAggCore's `show` uses
`pyplot.show`... but `pyplot.show` is defined as calling the backend
module's `show`, so it comes down to the same.
Still it's useful for them to be subclasses rather than straight
aliases, to keep the possibility of a canvas->manager mapping.
No need to explicitly mark WebAggCore as `supports_blit`, as that's
autodetected now (one can easily check that
`FigureCanvasWebAggCore.supports_blit` is still True).
Saving `pgf` to a BytesIO actually works fine nowadays, and can indeed
by manually tested on WebAgg.
0 commit comments