I''m going to submit a patch that will call wxInitializeStockObjects wxInitializeStockLists wxInitAllImageHandlers in wx.cpp on startup. I''ll remove the calls from all the samples. Does anyone have any beef with this? Roy
Roy Sutton wrote:> I''m going to submit a patch that will call > > wxInitializeStockObjects > wxInitializeStockLists > wxInitAllImageHandlers > > in wx.cpp on startup.+1
Alex Fenton wrote:> Roy Sutton wrote: >> I''m going to submit a patch that will call >> >> wxInitializeStockObjects >> wxInitializeStockLists >> wxInitAllImageHandlers >> >> in wx.cpp on startup. > +1I''m also +1, at least for now. Eventually we may want to create "light" or modular versions of wxruby that wouldn''t consume the time and memory needed by all those objects and handlers. But for now I think it is consistent with our philosophy to just "make it work" for people. Kevin
Apparently Analagous Threads
- [826] trunk/wxruby2/swig: Move RubyStockObjects back to App.i to avoid lots of error msg on GTK
- [804] trunk/wxruby2/swig: Initialise stock colours (eg Wx::RED), pens and brushes when wxruby2 is
- picture organizer -- need a bit of help
- QQ plots and boxcox
- Handling int pointer parameters