From: John H. <jdh...@ac...> - 2005-03-20 23:15:19
|
>>>>> "Matt" == Matt Newville <new...@ca...> writes: >> From my point of view, the decisions and consequences of Matt> interactivity should not be in backend_*, but in the code Matt> exposing the interactivity. If pylab needs to Matt> auto-magically create a wxPySimpleApp, do it in pylab where Matt> it won't bother anyone else. I totally agree with everything you said. wxapp should not be instantiated at module level in backend_wx. Unfortunately, doing it at show level breaks win32 pylab users -- in fact it segfaults with narry a helpful traceback to guide. I think the current situation (wxapp at module level) is a bug and should be fixed. I simply don't have the resources to do it myself. Someone needs or do the dirty work of getting it organized in a way that works across platforms and idioms (pylab versus app development). wx is still broken on OS X (the toolbar icons look bad). I would be very thankful if you would help with this -- it's just that we have to make sure that fixing one thing doesn't break something else, and that changes need to be tested on win32, linux and OS X in applications and in pylab. Admittedly, that is a lot of work: 3 operating systems and 2 modes is 6 combinations. But this is just one of 5 GUIs matplotlib supports, so I hope you can appreciate why I can't do it myself. Thanks! JDH |