<p dir="auto">Hi,</p>
<p dir="auto">I have been running into a recurring issue with the test code below (I am just quoting the most minimal version but the issue manifests itself every time pyplot is invoked). I have been running matplotlib 3.4.3 on Visual Studio Code (which freezes and needs manual restart) and jupyter-lab ("The kernel appears to have died. It will restart automatically").</p>
<p dir="auto">import matplotlib.pyplot as plt<br>
plt.plot([1,2,3], [1,2,3])<br>
plt.show()</p>
<p dir="auto">On jupyter-lab, the above code also generates a deluge of runtime warnings (which I am happy to send them in a separate file).<br>
I have tried removing and reinstalling matplotlib (multiple times) but the issue reproduces itself.<br>
I am really not sure how to approach this. The code was working fine until a few weeks ago, at which point I am not sure what changed. I am running this on a Windows machine (arm64 architecture).</p>
<p dir="auto">Thanks for any help, advice, or insight!</p>
<p dir="auto">If you assign any of the text fields in the figure options dialog to a "color-like" string, it changes into a color field the next time you open the dialog. This happens even in some not-so-obvious cases, like the letter 'y' (which you'd think you'd be able to use for a y axis label). This would be a little difficult to fix since the form dialog code is pretty complex, but a quick solution would be to only consider #ffffff style strings as colors, and add a helper function to convert the color properties to this format. a better solution would be to either wrap the color properties in an object, or add some kind of disambiguation parameter to the form parser (as an optional third entry in each tuple, i.e. "('Color', line.get_color(), 'color')").</p>