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
Expected behavior: Once plotted, jupyterlab should return to "idle" mode (when the mouse is not moving)
Actual behavior: Once plotted, jupyterlab switches between idle and busy very rapidly and loads the CPU.
Equivalent steps in matplotlib
Please make sure this bug is related to a specific proplot feature. If you're not sure, try to replicate it with the native matplotlib API. Matplotlib bugs belong on the matplotlib github page.
Hi, this is probably related to #76. The problem proplot has with these interactive backends is its complicated geometry/layout algorithm updates subplot positions and figure sizes automatically... but the backends trigger these updates constantly.
I added support for %matplotlib notebook backend by (necessarily) disabling auto figure resizing, but after an hour of trying I couldn't get ipympl installed on my machine. However I think 38290e7 might solve the issue -- it disables auto-figure-sizing when ipympl is the backend.
Try out the development branch with pip install git+https://github.com/lukelbd/proplot.git if you're still interested.
Description
Proplot plots make busy jupyterlab all the time.
Steps to reproduce
A "Minimal, Complete and Verifiable Example" will make it much easier for maintainers to help you.
Expected behavior: Once plotted, jupyterlab should return to "idle" mode (when the mouse is not moving)
Actual behavior: Once plotted, jupyterlab switches between idle and busy very rapidly and loads the CPU.
Equivalent steps in matplotlib
Please make sure this bug is related to a specific proplot feature. If you're not sure, try to replicate it with the native matplotlib API. Matplotlib bugs belong on the matplotlib github page.
Proplot version
Proplot: 0.6.1
Matplotlib: 3.3.1
jupyterlab: 2.2.6
ipympl: 0.5.7
The text was updated successfully, but these errors were encountered: