I am still hunting the bug where the cell editor finishes and crashes on Mac OS. In the process I have gone over these Grid related classes in great detail and found most were %importing wxObject.h and wxEvtHandler.h and they were not needed. I added a *.i file for ClientDataContainer not sure if it is needed out side Grid. I also added GridCellCoords. Sean _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users
I finally applied all these. Wow, that''s a perfect example of where darcs or bzr would be better than CVS...having to manually copy 4 files and run patch 21 times was no fun at all. I suppose it could all be automated, but still. Pushing a button to suck it all in at once should be so much nicer. Sean Long wrote:> I am still hunting the bug where the cell editor finishes and crashes > on Mac OS.Bummer. As I think I said, if you can narrow it to a small code sample, I can try to help isolate it. Kevin
> Sean Long wrote: > > I am still hunting the bug where the cell editor finishes and crashes > > on Mac OS. > > Bummer. As I think I said, if you can narrow it to a small code sample, > I can try to help isolate it.The Grid sample (GridSimple.rbw) in BigDemo has this bug and it only uses the default cell editor and render. Hopefully a fresh pair of eyes may find the problem. Sean
Sean, Could you be a little more specific about what the bug is? The only one I''m sure about right now is if you hit the delete button. Could you give me some steps to reproduce the problem you''re seeing? Roy Sean Long wrote:>> Sean Long wrote: >> >>> I am still hunting the bug where the cell editor finishes and crashes >>> on Mac OS. >>> >> Bummer. As I think I said, if you can narrow it to a small code sample, >> I can try to help isolate it. >> > > The Grid sample (GridSimple.rbw) in BigDemo has this bug and it only > uses the default cell editor and render. Hopefully a fresh pair of > eyes may find the problem. > > Sean > > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > >
Nevermind, I just didn''t read it well. Feeling a little bit slow today. Roy Sutton wrote:> Sean, > > Could you be a little more specific about what the bug is? The only one > I''m sure about right now is if you hit the delete button. Could you > give me some steps to reproduce the problem you''re seeing? > > Roy > > Sean Long wrote: > >>> Sean Long wrote: >>> >>> >>>> I am still hunting the bug where the cell editor finishes and crashes >>>> on Mac OS. >>>> >>>> >>> Bummer. As I think I said, if you can narrow it to a small code sample, >>> I can try to help isolate it. >>> >>> >> The Grid sample (GridSimple.rbw) in BigDemo has this bug and it only >> uses the default cell editor and render. Hopefully a fresh pair of >> eyes may find the problem. >> >> Sean >> >> _______________________________________________ >> wxruby-users mailing list >> wxruby-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/wxruby-users >> >> >> >> >> > > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > > >
Sean Long wrote:>>Sean Long wrote: >> >>>I am still hunting the bug where the cell editor finishes and crashes >>>on Mac OS. >> >>Bummer. As I think I said, if you can narrow it to a small code sample, >>I can try to help isolate it. > > > The Grid sample (GridSimple.rbw) in BigDemo has this bug and it only > uses the default cell editor and render. Hopefully a fresh pair of > eyes may find the problem.Sorry it has taken me so long to get to this. Ugh. GridSimple is...well...simple. There''s almost nothing there. Until proven otherwise, I would guess that the problem is actually in wx itself, and not in wxruby. Can you try a C++ wx grid sample and see if it has the same problem? Next most likely would be something in our event/callback system. I looked through all the grid event definitions and nothing looked obviously incorrect. You might put printfs in EventThunker (EvtHandler.i) to see if it is crashing during an event. Kevin
> Ugh. GridSimple is...well...simple. There''s almost nothing there. Until > proven otherwise, I would guess that the problem is actually in wx > itself, and not in wxruby. Can you try a C++ wx grid sample and see if > it has the same problem?Just tried the c++ grid sample and it has the same bug. In a way I am glad because it means the grid code in wxruby is correct but I am bummed because I still have the bug. I also looked in the wxWidgets bug tracker and found the same problem listed for wxPython and the submitter fixed it by going back to 2.6.0. I am going to install 2.6.2 and see if the problem is fixed. Should have tried this sooner. Sean
This bug is fixed in 2.6.2, atleast the c++ sample. I will compile wxruby and try the sample in ruby to make sure it is also fixed there. Thanks for the help and suggestions Sean On 10/9/05, Sean Long <sean.m.long at gmail.com> wrote:> > Ugh. GridSimple is...well...simple. There''s almost nothing there. Until > > proven otherwise, I would guess that the problem is actually in wx > > itself, and not in wxruby. Can you try a C++ wx grid sample and see if > > it has the same problem? > > Just tried the c++ grid sample and it has the same bug. In a way I am > glad because it means the grid code in wxruby is correct but I am > bummed because I still have the bug. I also looked in the wxWidgets > bug tracker and found the same problem listed for wxPython and the > submitter fixed it by going back to 2.6.0. I am going to install 2.6.2 > and see if the problem is fixed. > > Should have tried this sooner. > > Sean >
> This bug is fixed in 2.6.2, atleast the c++ sample. I will compile > wxruby and try the sample in ruby to make sure it is also fixed there.Works in wxruby too. Sean
Sean Long wrote:>>This bug is fixed in 2.6.2, atleast the c++ sample. I will compile >>wxruby and try the sample in ruby to make sure it is also fixed there. > > > Works in wxruby too.Good to hear. Thanks for the follow-up. We''ll have to keep that in mind when we encounter other obscure problems in the future: Problems are much more likely to be in the wxruby side, but the C++ wx code isn''t necessarily bug-free either. Thanks, Kevin