Displaying 20 results from an estimated 10000 matches similar to: "Patch to rakewx.rb"
2006 Oct 13
2
rakewx
With the recent check-in I accidentally committed my change to rakewx to
remove the -fvirtual swig option. -fvirtual is incompatible with SWIG
1.3.30. It''s not necessary (as I recall) for 1.3.29 but only reduces
the size of the wrapper code slightly. If anyone feels strongly about
this I can make it conditional on the SWIG version but simply removing
it seems the safest and
2006 Aug 24
4
SWIG
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
2006 Sep 20
3
Fix for non-centered windows
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
2006 Oct 21
2
common.i patch
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:
2006 Apr 18
12
Update on SWIG
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)
2005 Aug 07
1
Can''t rake without swig
You can''t rake without swig now. I keep swig out of my path so I can do
a build without swig to be sure it works with the download.
Exception `Errno::ENOENT'' at ./rake/rakewx.rb:20 - No such file or
directory - swig -version
No such file or directory - swig -version
./rake/rakewx.rb:20:in ``''
./rake/rakewx.rb:20:in `have_good_swig''
./rake/rakewx.rb:254:in
2006 Mar 27
4
Patch for Swig 1.3.29
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
2007 Apr 14
0
[967] branches/wxruby2/wxwidgets_282/rake/rakewx.rb: Fix two warnings generated by the rakefile
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2006 Sep 24
4
SWIG exceptions
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 *''
2006 Sep 12
6
Scintilla
wxScintilla already comes with a SWIG friendly header file. I modified
the rakewx and the Scintilla.i file to include it directly from the
wxScintilla install. This means it''s an odd-ball compared to our other
classes. Does anyone see a problem with this? I think it''s best to use
the one supplied with the installation to avoid problems of the header
file getting out of
2006 Aug 23
6
Looking for volunteers (no C++ knowledge needed!)
I just posted a follow-up to our bug that old SWIG versions are not
properly detected, leading to unclear failure messages:
---
Actually, this just got a lot simpler. We used to support both 1.3.25+
and 1.3.24-, so we had to do both kinds of detection. Now, we REQUIRE
1.3.29, and therefore any SWIG that can''t give us its version number the
new way is automatically too old.
We can get
2005 Sep 15
1
wxScintilla
I was fiddling around with wxScintilla tonight and I added it to
wxRuby. I haven''t gotten it really nicely integrated since I wanted to
make it an optional component. Nicely, wxScintilla was built with SWIG
in mind so [most] everything swigged beautifully after a little
touch-up. I may fiddle with this some more if you guys think it would
be worth adding to wxRuby2.
Any thoughts?
2006 Sep 22
1
trackobjects and SWIG 1.3.30
I have some conditional code based on the SWIG version. Current
versions of SWIG 1.3.30 still don''t fix %trackobjects correctly so I''m
going to remove the test for now so it builds correctly with my version
of SWIG. Hopefully before 1.3.30 is released we''ll have a better
trackobjects in SWIG.
Roy
_______________________________________________
wxruby-users
2005 Aug 19
6
Listbook patch
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
2006 Apr 23
4
*INPUT/*OUTPUT params patches
Hi
The attached patches enable the use of SWIG''s *INPUT *OUTPUT and *INOUT
typemaps as described in the manual. It''s done by including SWIG''s own
''typemaps.i'' file so it''ll allow us to benefit from future upgrades to that.
The problem was a collision between a Ruby macro _ (fixing for old
compilers) and a WxWidgets macro _ (for text
2006 Apr 23
12
Patches for object tracking
The following patches implement object tracking. Note nasty games I
play to make the tracking global. SWIG 1.3.30 won''t need this. I also
updated the minimum required SWIG version to 1.3.29.
Roy
_______________________________________________
wxruby-users mailing list
wxruby-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/wxruby-users
2006 Sep 24
2
Patch to fix get_event_object
This patch will fix the files so that SWIG returns the correct object
when get_event_object is called. I think I had submitted part of this
before but it looks like I either forgot to sync or it hasn''t been
applied yet.
Roy
_______________________________________________
wxruby-users mailing list
wxruby-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/wxruby-users
2006 Sep 06
12
Patch to wxWindow.h
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
2005 Aug 11
2
Patch file for FileDialog.i
Attached is a patch file for FileDialog.i. It doesn''t work 100% yet
because I haven''t yet figured out how to make it put the ruby
declarations in the right place. If I cut and paste the
rb_define_methods into the right place this works perfectly.
This patch fixes the dialogs.rb multiple select example so that
get_paths and get_filenames returns a ruby array. Note that I
2004 Jun 10
2
Building wxruby-swig on WinXP
Sorry for the lameness, but I need things explained to me very slowly...
-----Original Message-----
Subject: RE: [Wxruby-users] wxGrid Question
>
> Yes, grab the latest tarball from the above location. Then, you should
> install rubygems if you haven''t already:
> http://rubyforge.org/projects/rubygems/
>
> That should allow you to easily install rake:
>