similar to: App.i patch

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

After creating and installing a gem I get ''unintialized constant Wxruby2'' when trying to run wxRuby. Kevin, can you give me some pointers on getting this thing working? Roy

How''d we get listed on the top page of projects for Ruby? (See right side below ''Top Ruby Projects'') :) 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 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

Hi I''m pleased to let you know that wxruby2-preview 0.0.36 is now available on Rubyforge. Binary gems to follow... To check out a clean copy from SVN and build from source: svn co svn://rubyforge.org/var/svn/wxruby/tags/wxruby2/0.0.36 cd 0.0.36 rake gem WXRUBY_VERSION=0.0.36 From my reading of SVN docs it''s probably wise for developers to checkout anonymously as a bit of

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

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

Doing some comparison to older builds of wxRuby2 I see that some things work better now and some worse. I wish I could pin down exactly where things went wrong in one case. I will try doing some comparison to recent changes to see if I can find a solution to those problems. I''d really like to get this alpha release done ASAP. Roy

Hi all, How soon can we do our alpha (binary gem) release? 1. I would like to get the samples working a bit better, but am ok simply documenting most of the current problems. Do the samples crash every few minutes for other people? Or is it just me? I would like to have a copyright/license comment at the top of every sample file before the alpha release. 2. I would like to receive and merge a

I see several shortcomings in our current method of compiling on linux. Some things I ran in to which might need to be documented on the wiki: 1) Compiling wx properly. A little discussion of the proper flags would be helpful. 2) The use of system libraries for jpeg, tiff and png. The rake file assumes you''ll need these, even if you''re using the builtins from wx. We

I think it''s time to get me onto the project at rubyforge so I can subscribe to the bug tracker. As we move forwards with more maintenance oriented tasks it will be helpful to be able to patch directly to SVN. For now, I''ll keep submitting patches to the list. Roy

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

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

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