In the dialogs.rb sample, when you click the delete button you get: C:/RubyDev/wxruby2/samples/dialogs/dialogs.rb:61:in `onButton'': undefined method `free'' for #<Wxruby2::Button:0x36474b8> (NoMethodError) Should all/some wxObjects have a free function? how do we intend to handle this?
Roy Sutton wrote:> In the dialogs.rb sample, when you click the delete button you get: > > C:/RubyDev/wxruby2/samples/dialogs/dialogs.rb:61:in `onButton'': > undefined method > `free'' for #<Wxruby2::Button:0x36474b8> (NoMethodError) > > Should all/some wxObjects have a free function? how do we intend to > handle this?I don''t think we should implement a ''free'' method unless wxPython also does. Perhaps later, when we have all the memory management figured out, I might feel differently. For now, I would delete that line from the sample. Thanks, Kevin
Kevin, I''m beginning to run out of ''low-hanging fruit''. There are still dozens of things left to do but I wanted to see if perhaps you wanted to lay out a roadmap to the next ''release''. The way I see it, the biggest impediments to powerful, working programs are: 1) Functions that return wx objects that have already been created instead create new objects 2) The remaining segfaults on exit (minor?) Would you like to st some direction for us here? Roy Kevin Smith wrote:> Roy Sutton wrote: > >> In the dialogs.rb sample, when you click the delete button you get: >> >> C:/RubyDev/wxruby2/samples/dialogs/dialogs.rb:61:in `onButton'': >> undefined method >> `free'' for #<Wxruby2::Button:0x36474b8> (NoMethodError) >> >> Should all/some wxObjects have a free function? how do we intend to >> handle this? >> > > I don''t think we should implement a ''free'' method unless wxPython also > does. Perhaps later, when we have all the memory management figured out, > I might feel differently. For now, I would delete that line from the sample. > > Thanks, > > Kevin > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > >
Roy Sutton wrote:> Kevin, > > I''m beginning to run out of ''low-hanging fruit''. There are still dozens > of things left to do but I wanted to see if perhaps you wanted to lay > out a roadmap to the next ''release''.Good idea.> The way I see it, the biggest impediments to powerful, working programs are: > > 1) Functions that return wx objects that have already been created > instead create new objects > 2) The remaining segfaults on exit (minor?)I agree, except that the segfaults don''t seem that minor to me. I suspect if we were to insert gc.start calls here and there, those segfaults would happen right then. When we fix this, I would be willing to cut a "preview release" with binaries. One other issue is all the methods that return objects (instead of object pointers), which I believe swig is ignoring for now. You seem to have a pretty good grasp of typemaps, so I would appreciate if you could take on this one at some point. I just updated the TODO list to reflect your thoughts, and my response. Kevin