similar to: Part 5

I have basically spent a full day''s worth of time I could have spent working on something productive trying to figure out which function signature I changed that is causing wxRuby to crash. It just takes so long to recompile this from scratch and without dependencies you kind of have to when you change wxWindow.h. I updated a lot of signatures to match the wxWindows header file.

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

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

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

Does anyone know if the XRC hand-coded methods in Window.i are still required after my recent change to return the correct types? Also, given that wxWindow.h is included all over the place, I think we need to move some of that stuff out into a common .i that''s included for all wxWindow descendants. Roy

This patch file takes advantage of the parameter name change I made in wxWindow.h _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

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

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

I have not worked on wxRuby2 for awhile and decided to download the latest CVS HEAD and saw that it still had a problem with wxWindow::GetTextExtent (in my case showing up when editing Grid cells). So I copied the method signature from the wxDC::GetTextExtent which seems to be working, changed 2 variable names and made the typemap the same as used for wxDC. Well in my program editing grid cells

Forwarded from the SWIG mailing list, so we have a copy in our archives. Kevin -------- Original Message -------- Subject: Re: [Swig] Re: Object return problem Date: Sun, 09 Oct 2005 18:31:40 -0400 From: Kevin Smith <wxruby@qualitycode.com> To: Charlie Savage <cfis@interserv.com> CC: Swig@cs.uchicago.edu References: <4347277E.1030700@mindspring.com>

Take a look at the generated code from ListBox.cpp: static VALUE _wrap_new_wxListBox__SWIG_0(int argc, VALUE *argv, VALUE self) { VALUE arg1 ; wxWindow *arg2 = (wxWindow *) 0 ; wxWindowID arg3 ; wxPoint *arg4 = 0 ; wxSize *arg5 = 0 ; int arg6 ; wxString *arg7 ; long arg8 ; wxValidator *arg9 = 0 ; wxString *arg10 = 0 ; wxListBox *result; wxString

Here''s a patch for FileDialog.i. Seems we had never removed that #ifdef in there. wxWindows 2.6.2 works just fine on Windows. No other news. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

Hi, I started developing with wxRuby with the 0.1.0 release, and have been very pleased. As a ruby and wxWindows fan, I was happy to see the wxruby project, and have been very impresed with the implementation. I''ve been working on supporting the XML resources (wxXRC), and have an issue I''d like some advice on. XRC plugged in very nicely, and I was able to query resources.

Hello all. This gets past the problem in bigdemo where it won''t start the application at all. That was where it was overflowing the stack on get_label. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

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

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

In diagnosing the wxWindow.h problem I discovered that the problem is related to directors wrapping returned pointers. I went in to wxMDIParentFrame and removed ''virtual'' from a couple of the functions and the MDI windows work again. I will investigate a fix for this later, since there are a lot of functions that return pointers. However, the MDI crash was a big one that

Hi, I am making a game with Ruby/SDL and have run into trouble finding a GUI to cooperate. I have seen numerous examples of wxWindows in combination with SDL (wxPython and PyGame), but have yet to be able to do it in ruby (PyGame example: http://wiki.wxpython.org/index.cgi/IntegratingPyGame). I am not very good with wxRuby as this is my first time using it and thought some more knowledgable users

wxMenuItem.h patch This patch adds in some platform-specific functions, #if defined out so it should compile properly on other platforms. Note: This will get a couple demos working properly on Windows and GTK. The demos will need to have platform specific calls in there. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org

About a year ago (ouch!), Robert Carlin submitted a ported version of the wxPython demo/sample. I hoped to include it in wxruby2, but it relies on SplitterWindow, which isn''t in wxruby2 yet. I tried to implement SplitterWindow myself, but got such strange results that I''m thinking I did something wrong. Even though the generated C++ code specified a variable number of