Daniel -
Yes that works. In my case - I hate to edit any existing third party
code bases - or it bites me later when I upgrade.
For now - I simply do my own dead reference clean up externally when
doing the deletes. Really, that would be the same as just doing a
disconnect - but for othe
Here is a bit more detail and a simple example.
The example below places red squares in an axes. When the user clicks on an
existing red square - another square is created and added. When the user hits
any key a square is deleted from the axes. The error is triggered by clicking
on the red sq
Within matplotlib.cbook.CallbackRegistry both the connect() and process()
methods check for dead references when called. If a reference is dead it
deletes it from the callback list.
I have found a situation where this presents a problem.
First, a "button_press_event" calls the process method()
