similar to: ColourDialog

Bonjour Alex. Je voudrais savoir si il est possible de sauvegarder les couleurs quand on se sert de "ColourDialog"? merci Sebastien _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

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

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)

The result of the compilation after installing swig results in lots of errors of the sort: WindowDisabler.obj : error LNK2001: unresolved external symbol _SWIG_Ruby_ConvertPtr I can see this is defined in rubydef.swg but I''m not sure why this isn''t just included in the files that need it. Can any swig experts tell me what I need to do to progress? I''m using

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:

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

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

The documentation for Wx::FileDialog is incorrectly generated: http://wxruby.rubyforge.org/doc/filedialog.html Every time the ''*'' (for the wildcard character in file filters) appears, the doc instead switches between boldface and normal. Also, it seems like the links under "See also" are broken. Feature request: Regarding all modal common dialogs (ColourDialog,

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

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

wxRuby 0.5.0 has been released and is now available for download from RubyForge at http://wxruby.rubyforge.org/ This release includes binary builds for Max OS X and MS Windows. Please report any bugs or feature requests here: http://rubyforge.org/tracker/?group_id=35 Changes in this release include: * Added XRC (Xml Resource File) support. * Added totally awesome HTML widget from Tobi

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

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

Hey guys, I''m really sorry to be so out of touch these days. We just hired two new programmers at work so I''m busy bringing them up to speed...in time for them to help us get a major release out at the end of the year. So my personal goals for wxruby participation at the moment are: 1. Respond to any support requests as quickly as possible 2. Respond to any questions from you

Hi all, Ruby 1.8.1 Solaris 9 wxwindows 2.4.2 (package from blastwave.org) wxruby 0.3.0 I''m having trouble getting this sucker to build on my Solaris box. Here''s how I''m building: ruby extconf.rb --with-xrc-dir=/opt/csw --with-xrc-include=/opt/csw/lib/wx The include directive I added because the setup.h file is there (for whatever reason). And yes, /opt/csw/bin and

Hi all Have been taking a look at the samples to see what''s broken. Not looking TOO bad overall, but a few problems we should try and tackle before alpha: Firstly, I have a few commits (minimal, dialogs, unicode) - anyone else been working on these or can I go ahead? One general issue is that many of the samples rely on being run from their own directory, but don''t enforce

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

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