similar to: wxruby2 swig retooling "complete"

I finally gave up on swig 1.3.22, since it seems to be causing too many problems. Ubuntu breezy will have 1.3.24, so I''m retargeting wxruby2 to swig 1.3.24+. At the moment, I have 1.3.25 on my system, since that''s the current release. I''m finding all kinds of problems with the post-processors we have that clean up the .cpp files that swig creates. The

I just checked out a fresh copy and had to tweak wxIcon.h to get it to compile on Mac OS X and windows. The problem is with: wxIcon(const wxString& filename, wxBitmapType type = wxBITMAP_TYPE_XPM, int desiredWidth=-1, int desiredHeight=-1); that signature is only used on GTK on other systems it is: wxIcon(const wxString& name, long

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 was investigating why the find dialog causes an error when you close it. It seems that wxRuby2 is returning a new ruby object when you call Event.get_dialog. This causes some big problems when you''re expecting you''re going to get back the same ruby pointer that you put in. In a brief check over the source I don''t see anything that preserves the original ruby

Hello all. I decided to see how things were progressing and have updated my Swig to 1.3.29 and my wxWindows to 2.6.3. I''ll try rebuilding everything as soon as I''m done compiling wx 2.6.3. Then I hope to have some time to read up on the new ruby stuff in Swig to see if we can close the last few holes. Roy

Hey everybody, I''ve made some progress on wxruby-swig, and have some good news and some bad news. The good news is that the MSVC version finally can run all of the samples provided in CVS. I''m using the same solve-by-ignore solution to the GC problem that wxruby uses, so there is far less crashing goin'' on. Depending on the next few weeks, we might be able to

I see that this problem was noted a while ago (http://rubyforge.org/ tracker/index.php?func=detail&aid=251&group_id=35&atid=218) but it seems not to have received much attention. Any chance that it will be looked at anytime soon? So far, I prefer wxRuby to Ruby/Tk because of that closer coupling with the native window manager. However, the memory leak is just murdering me.

Was trying to understand more about the internals of wxruby-swig, where does the big chunk of XML comes from? I saw something similiar in Python, is that massaged out of there? The codes produced by extractxml.rb and wxclasses-2.4.2.xml is quite different from the original header files. Just for example the WxDialog class. OnXXX are non-virtual in WxWidgets, but virtual in wxruby-swig

I have a minimal working version of a SWIG-based wxRuby that can bring up an empty Frame with a title. On my system, it crashes on exit. I suspect this is the same problem that I mentioned months ago when I first upgraded to wxWindows 2.4.2. The problem mysteriously vanished at some point, but now it is back. I fiddled with this new code for several frustrating hours, and couldn''t

I''ve spent a couple hours tracking through the code and reading Swig documentation to try to find out about tracking C objects back to Ruby objects. It''s not so easy to do. I took at look at wxPython and their source is a mess! I wasn''t able to glean anything from them on how they do it. My current hypothesis is to trap SWIG_NewPointerObj calls and build a map.

Grabbed 0.0.16 and tried a build for kicks. ...all good, except for a warning in MenuBar.cpp, then... g++ -c -I/usr/local/lib/wx/include/mac-2.4 -D__WXMAC__ -DWXMAKINGDLL -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -fno-common -fno-common -pipe -fno-common -x objective-c++ -I /usr/local/lib/ruby/gems/1.8/rake-0.3.2/lib -I /usr/local/lib/ruby/site_ruby/1.8 -I

Hi everyone, As Kevin has just announced, wxruby-swig has been moved into CVS as a toplevel project. It still is not in a "releasable" form yet, but it now builds on more systems than it doesn''t, and is moving towards stability. Because of the complexity of the build environment, we''re using rake (http://rake.rubyforge.org) as a build system instead of the standard

For debug builds we define __WXDEBUG__ and WXDEBUG=1. In the swig code we add a check for wxDEBUG to directors. My guess is we mean for one of those defines to be the other. Which one should we change? wxDEBUG-> WXDEBUG or WXDEBUG-> wxDebug? Roy

Have tracked down a fairly serious cause of memory leakage in wxRuby2. swig/fixdeleting.rb adds a hash mapping from pointer address to ruby VALUE in every director initialiser using GcMapPtrToValue. The problem is that being a value in this global hash means that every Wx::Bitmap (for example, and others) are always marked in ruby''s GC mark phase, so they are never collected until

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

(Mostly for Roy): I saw this on the SWIG list, and wonder if it might be related to the problems we have been seeing where multi-arg typemaps end up invoking the wrong wrapper methods. (Not the newly-discovered directorout stuff). Perhaps if we switched to "compactdefaultargs" things would start to work more sanely. Looking at this section of the SWIG docs, it looks like it should

Greetings all, As you have noticed, I have been largely absent from the wxruby team for quite a while now. Fortunately, others have taken charge and continued to move wxruby forward. It''s still a great project, but I just can''t participate right now. I will be unsubscribing from both the dev and users mailing lists in a couple days. Because I will be packing for a long trip

Anyone on the list have some pointers for getting swig working properly on Windows? Anytime I reswig a file it breaks wx.cpp. I''m sure I''ve got a setup problem but I haven''t been able to put my finger on it yet. Roy

REMINDER: wxruby-swig is an experimental rewrite of wxRuby, using SWIG. It is not yet useful. The official wxRuby is still at 0.2.1. The 0.0.3 release of wxruby-swig is able to run the "minimal.rb" sample, which includes menu event handling. As always, it is available at: http://qualitycode.com/repos/wxruby-swig/ I also created a tarball this time, so you can just download that and

Hello, I am a newbie to wx and wxruby, I just built wxruby2 on my gentoo box. At first it did not work. So I post a little message,it might help others. At first a cryptic message was shown SWIG Version 1.3.21 Copyright (c) 1995-1998 University of Utah and the Regents of the University of California Copyright (c) 1998-2003 University of Chicago Compiled with i686-pc-linux-gnu-g++