similar to: SWIG

SWIG 1.3.29 isn''t going to cut it for us. We''ll have to wait until 1.3.30, unless I can hack together a nasty workaround for a problem with the object tracking. It seem that each SWIG module gets its own hash for tracking objects. This means that, for example, you create a find dialog (in FindReplaceDialog.cpp) events you get from it (from FindDialogEvent.cpp)

I was trying to fix the problem with wxImage and the char */unsigned char * thing today and I was going to hand-write the functions to translate between the two. While doing so I decided I''d clean up the SWIG error message to make it more clear. Here''s an example SWIG-generated argument error: in method SetData'', argument 2 of type ''wxImage *''

Two patches here: First one removes virtual from a function that shouldn''t have been virtual. Second one applies a typemap to catch GetRectFromChildWindow. For reasons that are completely beyond me the standard ruby OUTPUT typemaps don''t define directorargouts. I will take a stab at patching SWIG''s default typemaps someday so we get this fixed for free on all our

The latest cvs version of SWIG breaks a few things. I have patched common.i to fix most of it. There will be some other things later that should be compatible with all versions. Can someone test to see if this compiles with the old version? Roy -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: common.i.patch Url:

Small patch to correct spelling of lemonade. Should ask Sean if he really wanted it to be lemonaid. If not, here''s the patch. On another note... This sample works! Kudos. It is odd that the textbox doesn''t scroll. I suppose I may patch that, too. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org

Attached is a patch for Swig that at least allows us to link the library. I am experiencing a number of bugs that will need to be tracked down and squashed. I haven''t even had time to look at the newer Swig features yet. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

The result of the compilation after installing swig results in lots of errors of the sort: WindowDisabler.obj : error LNK2001: unresolved external symbol _SWIG_Ruby_ConvertPtr I can see this is defined in rubydef.swg but I''m not sure why this isn''t just included in the files that need it. Can any swig experts tell me what I need to do to progress? I''m using

What do you think about adding a shebang line to the samples so they can be launched on linux/mac like you can on windows? Roy

http://visualwx.altervista.org/ A visual builder for wxWindows that purports to support Ruby. I''ll play with this some and see if I can design projects that work with wxRuby2. Roy

Swig is making mincemeat out of ComboBox.new. Because of the way it''s picking the ''correct'' one to call it''s calling with a null name instead of a default name. How did we fix this before?

How''d we get listed on the top page of projects for Ruby? (See right side below ''Top Ruby Projects'') :) Roy

I was fiddling around with wxScintilla tonight and I added it to wxRuby. I haven''t gotten it really nicely integrated since I wanted to make it an optional component. Nicely, wxScintilla was built with SWIG in mind so [most] everything swigged beautifully after a little touch-up. I may fiddle with this some more if you guys think it would be worth adding to wxRuby2. Any thoughts?

I was investigating why the find dialog causes an error when you close it. It seems that wxRuby2 is returning a new ruby object when you call Event.get_dialog. This causes some big problems when you''re expecting you''re going to get back the same ruby pointer that you put in. In a brief check over the source I don''t see anything that preserves the original ruby

The following patches implement object tracking. Note nasty games I play to make the tracking global. SWIG 1.3.30 won''t need this. I also updated the minimum required SWIG version to 1.3.29. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

Wow. Look what SWIG does to GetTextExtent in Grid.cpp: void SwigDirector_wxGrid::GetTextExtent(wxString const &string, int *x, int *y, int *descent, int *externalLeading, wxFont const *font) const { ... if (swig_get_up()) { wxWindow::GetTextExtent(string,x,y,descent,externalLeading,font); return; } obj0 = rb_str_new2((const char *)(&string)->mb_str());

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?

Attached is a patch file for FileDialog.i. It doesn''t work 100% yet because I haven''t yet figured out how to make it put the ruby declarations in the right place. If I cut and paste the rb_define_methods into the right place this works perfectly. This patch fixes the dialogs.rb multiple select example so that get_paths and get_filenames returns a ruby array. Note that I

These files add the virtual function AcceptFocus that was missing from wxWindow.h. In order to make things right I had to make sure it was also declared in all the places where wxWindows also changes it. Also, in wxTextCtrl on Windows GetDefaultAttributes needs to be redeclared. I haven''t downloaded the Unix and Mac headers for 2.6.3 so I couldn''t see if it also applies

I''m trying to un-ignore TextCtrl#get_selection. The typemaps work fine, but in the process it breaks get_insertion_point. This is because (on Mac, tho not GTK), get_insertion_point calls get_selection internally and simply returns the first value. I think the return value is being converted from a long to a ruby int twice, because when get_selection is wrapped, it works fine but the

This patch fixes background color problems (at least on Windows). It uses the dreaded ''FIXME'' My plan for next weekend is to try building wxPython from the source to see how they manage to achieve several things with SWIG that we''re not (yet) able to. If I''m successful it might lead to wrapping a significant portion of wxWidgets more correctly than