For the most part, I think we have this with the GTK
> backend, but it may be necessary to refactor in order to get
> something that works with both. I'll think it over and take
> a look at the WX code to see if I get any ideas how to
> proceed.
I've made a number of changes to backend_wx that seem to work for the
with the interactive architecture as it currently exists. I still
think it will be useful to do some refactoring, even if only to make
the function names more intuitive, eg something like
import matplotlib
matplotlib.use('WX')
matplotlib.interactive_mode(True)
rather than
import matplotlib
matplotlib.use('WX')
from matplotlib.backends.backend_wx import ShowOn
ShowOn().set(True)
But in any case, here is a wx script that works with the changes I
made to backend_wx.py. Take a look at the changes, see if they pass
your unit tests, rewrite as necessary and then check them into CVS if
they look good
import matplotlib
matplotlib.use('WX')
from matplotlib.backends.backend_wx import ShowOn
from matplotlib.matlab import *
ShowOn().set(True)
figure(1)
plot([1,2,3,4])
xlabel('time')
savefig('test')
#show()
backend_wx.py (54.9 KB)