I have just committed a significant update to backend_wx.
> The intention is that this will be the basis of the
> backend_wx code in release 0.40 of Matplotlib. It contains
> numerous small fixes, but the highlights are:
This sounds great. It looks like everything is about ready to go.
One minor glitch. I just did an update to backend_wx Repository
revision: 1.15. When I launch a figure, eg
> python subplot_demo.py -dWX
The window comes up and looks properly placed and sized, but no image
appears in the figure window. I have the window, the toolbar etc,
only no axes, no plot. Hmmm.... RHL9, GTK2, wxPythonSrc-220.127.116.11.
When I click on the save dialog, it pops up, prompts me for a
filename, and then does noting -- no file is created.
Perhaps I have the older version of backend_wx (sometimes the CVS
mirrors are behind). If so, please send me the attachment.
Otherwise, if you have any insights, please let me know.
> I should note that performance of the double-buffered
> drawing backend is not as good as the previous GDI version
> (at least on Windows), although animated drawing will be
> flicker-free. I would be interested to hear opinions on
> whether people prefer double buffered drawing or GDI, and
> whether it makes sense to support both (as an option when
> creating a figure, perhaps).
If it's not hard to support both, why not. I prefer flicker free
navigation and animation over performance, and in most cases find the
performance of matplotlib acceptable (pcolor being a notable
exception). But I have a fast machine.
> Known bugs are:
> - Mousewheel (on Windows) only works after menu button
> has been pressed at least once. I do not plan to fix this
> since John is planning to rewrite the navigation code for
> backend_gtk to work more like matlab.
> - Mousewheel on Linux (wxGTK linked against GTK 1.2) does
> not work at all Suspect that this is a GTK 1.2 issue, but
> in any event, it's something else I don't plan to fix.
I'm not too worried about mouse wheel stuff for the first release,
especially with changes to the navigation bar approaching.
> John, is it worth activiating the Sourceforge bug tracker
> after 0.4 release?
I think it is active. There have been 4 bug reports and 1 patch there
already. I'm willing to go either way here. I find it easier to
check the mail list than the SF site, but I can train myself otherwise
if you think it's worthwhile to do so.