similar to: fixmodule patches

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

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

This patch adds %directorout typemaps for the GetTextExtent functions _______________________________________________ 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());

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

Hi Seems that the last round of commits makes bigdemo crash fairly quickly. Guessing it''s something to do with either the Window or fixmodule change. Program received signal EXC_BAD_ACCESS, Could not access memory. 0x00034fbc in rb_obj_is_kind_of (obj=3825080, c=1839676) at object.c:523 523 object.c: No such file or directory. Any hints? alex

Swig''s bad interface generation strikes again. get_text_extent called with 1 argument maps to WindowDC''s _wrap_wxWindowDC_GetTextExtent__SWIG_0 Since this generates a wxFont that''s not initialized to nil it fails when calling into wxWindows. Anyone have a suggestion?

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

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

Here''s a patch to fix Wx::Window#get_text_extent - it requires that the patches from teh last message are applied, to enable *INPUT etc typemaps. Roy - though the function works correctly when called from Ruby, it still causes a crash when called internally when clicking on a Wx::Grid cell. Saw your message on SWIG mailing list, hopefully someone there can help out. alex

StatusBar.i -- Adds a typemap to return a wxRect structure. You''ll really want to go over this to make sure it''s correct. I don''t have a sample but it did make part of one of the bigdemo samples work a little better. If you want to put this on the back-burner until we have a chance to test it more fully I''d understand completely. One of the things

This patch implements a more generic solution to the problem that will work for all our integer types at least. Use this instead of the last version I sent, please. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

I just posted a follow-up to our bug that old SWIG versions are not properly detected, leading to unclear failure messages: --- Actually, this just got a lot simpler. We used to support both 1.3.25+ and 1.3.24-, so we had to do both kinds of detection. Now, we REQUIRE 1.3.29, and therefore any SWIG that can''t give us its version number the new way is automatically too old. We can get

Ok so I made a lot of changes and the controls sample works pretty good now. What I changed or added: - Got all my modifications meshed into wxRuby2. - Added constructors to wxIcon.h - Changed Xrc.i to XmlResource.i and changed wxXrc to wxXmlResource within the file. I also had to change Xrc to XmlResource in rakewx.rb. - For backwards compatability with wxRuby 0.6 I added the subclass methods

There are several functions that take the parameters (int *x, int *y) In some cases x & y are simply return values. In some cases x & y are both input and output. How are we going to handle this properly? One method would be to change the header files to something like xin or xout. I don''t really like that method as it''ll break as soon as header files change.

Here''s an example of the problem I was talking about the other day. Take a look at Button.i. It imports from its entire heirarchy. If you look at Button.cpp you will see that no wrappers are generated for anything except the button functions. This brings up some other things that we''ll need to keep in mind: If we''ve created a typemap in a .i file in classes and

Hi all, I wanted to have a look at wxRuby on a recent version of ruby 1.9 (ruby-1.9.1-preview1) on Ubuntu 8.10 x86. Here is the result : chauk-mean at MyUbuntu:~/wxruby2$ ruby19 -v ruby 1.9.1 (2008-10-28 revision 19983) [i686-linux] chauk-mean at MyUbuntu:~/wxruby2$ rake19 WXRUBY_VERSION=1.9.9 gem (in /home/chauk-mean/wxruby2) Enabling DYNAMIC build Enabling RELEASE build Enabling UNICODE build

This patch for typemap.i fixes several swig warnings while compiling. You may noticed that I didn''t fix all the typecheck typemaps. I suppose I should fix all of them, but they don''t cause problems with the compilation. This also has a patch to convert void *''s into ruby numbers. This fixes a problem with the get_handle call. I still am not sure what''s

Hi Have been looking again at SWIG output pointer parameters, as: http://www.swig.org/Doc1.3/Ruby.html#Ruby_nn32 The problem is, whenever I tried to include the SWIG/Ruby ''typemaps.i'' file, it threw loads of errors. A bit more investigation pinned the problem down to some secondary files that typemaps.i includes to map ''special'' types like File. So I tried

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