similar to: Patch to fix get_event_object

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

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

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)

This patch to event.i (if it worked correctly!) would fix the problem of event types being returned a fox objects instead of a fixnum matching the constants expected. This patch has the same problem as the previous one in that you must manually move the ''get_event_type'' declaration down to where it belongs once the .cpp files is produced. If someone has pointers on how to

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:

This patch file will allow the MDI example to run. We''ll need to revisit it later. There''s still a crash but it''s the same crash as from the scrolled window example. I''ll send a patch later that fixes the problem with DrawLines. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org

I decided to try my hand at hacking SWIG and successfully produced a patch that fixes the error I demonstrated. I''m not -positive- it''s correct for all cases but I''ll re-run my version of SWIG over the library and see how things turn out. Roy

These patches (should) give us support for compiling against Ruby 1.9. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

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

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

This patch fixes up two problems with ArtProvider constants and fixes a small typo. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

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

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

This patch fixes the problem with the undefined constants. Apologies to Alex as I didn''t apply his patches yet. The fix is to just removed the _C from the end of the ones that won''t compile anymore. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

Attached are patches to make the textctrl.rb sample work fully. Note the new %directorargout typemap I added to fix wxWindows calling into SWIG. I don''t know if this can fix all such problems or not. Let me know what you think. I also rubified the sample a little bit more. Also, note that I fix the << operator so the function can be called. I hope I did this right. Roy

I think I had to do this to get the tarball to compile on Windows _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

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 *''

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

Hi, Has this problem been resolved? I encountered the same problem on my FC3 system with wxGTK-2.4.2 and wxruby-0.6. Thanks. Stephen [Wxruby-users] Re: Problem building wxRuby: htmlproc.h not found *Nick* devel at nicreations.com

Hi The attached patches enable the use of SWIG''s *INPUT *OUTPUT and *INOUT typemaps as described in the manual. It''s done by including SWIG''s own ''typemaps.i'' file so it''ll allow us to benefit from future upgrades to that. The problem was a collision between a Ruby macro _ (fixing for old compilers) and a WxWidgets macro _ (for text