similar to: Big Demo

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

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

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

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

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)

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

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:

The files checked out of SVN come out without the ability to be executed. So, I can''t run the samples without prefixing with ''ruby '' Before, the file associations allowed me to run samples just by putting the name on the command line. Can we fix this? Roy

The ColourDialog (Darn Brits messing up the spellings of perfectly good words!) has a weird behavior. When you first open it you can''t select a color from the ''rainbow'' on the right side until you select a basic color on the left. I don''t think this was the case before we did the big inheritance change. Does anyone else remember if it worked properly

This patch makes Unicode the default build for windows. You can override the default by setting a WXRUBY_NO_UNICODE environment variable. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

Tracing down some things to add in validators and I''ve run across something that kinda bothers me... In order to implement validators you have to override the clone method. The directors seems to be set up to specifically handle this situation. However, whenever C++ calls back to the object''s methods the swig_get_up function is returning false. It seems like swig_up

1) Please ignore the patch for wxMouseEvent.h. Including this causes the build to fail. 2) Attached are several files to patch some things to get the bigdemo working (better): Added a generic typemap for converting ruby arrays into point arrays. Added a typedef for wxDash Corrected/expanded the typemap for GetTextExtent Added GetMultiLineTextExtent prototype (there are some others missing I

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

I think we can mark this bug closed and check in the patch. Anyone have any concerns/questions before I do? Roy -------- Original Message -------- Subject: [ wxruby-Bugs-6144 ] error: cast from ?void*? to ?int? loses precision Date: Sun, 15 Oct 2006 08:37:31 -0400 (EDT) From: <noreply at rubyforge.org> To: noreply at rubyforge.org Bugs item #6144, was opened at 2006-10-15 00:04

I might be a bit scarce this weekend -- I managed to score a late ticket to RubyConf! I''ll be in Denver hobnobbing with Matz. :) Roy

We include wx/wx.h in a lot of places. It seems from a (very) cursory examination that the current method is to include wx/wxprec.h. Seems to work fine including wx/wx.h so this may be entirely a non-issue. Does anyone have any feelings on this? Roy

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

The file swig/classes/includes/wxLayoutConstraints.h may need to be updated. It''s missing centreX and centreY from the list of wxIndividualLayoutConstraints. I''d send a patch in but I''m wondering if this file just needs to be regenerated from scratch. Roy

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