similar to: *INPUT/*OUTPUT params patches

Daniel F. Savarese wrote: > In message <444C4D5B.6060801@mindspring.com>, Roy Sutton writes: > >> The patch didn''t apply for me. I have created a new patch for the two >> affected files. >> > > You probably needed a -p0 (assuming application from inside wxruby2/) > or we had slightly different versions of the source files or maybe > the

Wow. Look what SWIG does to GetTextExtent in Grid.cpp: void SwigDirector_wxGrid::GetTextExtent(wxString const &string, int *x, int *y, int *descent, int *externalLeading, wxFont const *font) const { ... if (swig_get_up()) { wxWindow::GetTextExtent(string,x,y,descent,externalLeading,font); return; } obj0 = rb_str_new2((const char *)(&string)->mb_str());

(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

Swig''s bad interface generation strikes again. get_text_extent called with 1 argument maps to WindowDC''s _wrap_wxWindowDC_GetTextExtent__SWIG_0 Since this generates a wxFont that''s not initialized to nil it fails when calling into wxWindows. Anyone have a suggestion?

Hi Have been looking again at SWIG output pointer parameters, as: http://www.swig.org/Doc1.3/Ruby.html#Ruby_nn32 The problem is, whenever I tried to include the SWIG/Ruby ''typemaps.i'' file, it threw loads of errors. A bit more investigation pinned the problem down to some secondary files that typemaps.i includes to map ''special'' types like File. So I tried

There are several functions that take the parameters (int *x, int *y) In some cases x & y are simply return values. In some cases x & y are both input and output. How are we going to handle this properly? One method would be to change the header files to something like xin or xout. I don''t really like that method as it''ll break as soon as header files change.

I have not worked on wxRuby2 for awhile and decided to download the latest CVS HEAD and saw that it still had a problem with wxWindow::GetTextExtent (in my case showing up when editing Grid cells). So I copied the method signature from the wxDC::GetTextExtent which seems to be working, changed 2 variable names and made the typemap the same as used for wxDC. Well in my program editing grid cells

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

Here''s a patch to fix Wx::Window#get_text_extent - it requires that the patches from teh last message are applied, to enable *INPUT etc typemaps. Roy - though the function works correctly when called from Ruby, it still causes a crash when called internally when clicking on a Wx::Grid cell. Saw your message on SWIG mailing list, hopefully someone there can help out. alex

This patch adds %directorout typemaps for the GetTextExtent functions _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

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

Daniel, Thanks for the sample code. Sizers do appear to have a problem and it''s on the list to take a look at. I''m currently reworking several classes and trying to fix some of the big compatibility bugs. I will test your code with my latest builds but I don''t think I''ve gotten to the sizers yet. Roy Daniel F. Savarese wrote: > I''ve run into

I performed a get on the CVS WxRuby2; I have installed wxWidgets 2.6.3 and SWIG 1.3.29. Additionally I am running Visual Studio on Windows XP. When I run rake to compile I receive the following error. App.cpp c:\wxWidgets-2.6.3/include\wx/platform.h(190) : fatal error C1083: Cannot open include file: ''wx/setup.h'': No such file or directory rake aborted! Command failed with

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

Hello guys, Alright Alex..... I need a few tips on where to start. I know that I''m going to need to rewrite the wxSocket header files, in order to incorperate them into wxRuby. But some advice on stuff such as wxSocketClient::new/connect, where it takes a wxIPAddress, and so forth. I know they are pretty friviolous structures for holding information about Addresses in which to make

This patch for typemap.i fixes several swig warnings while compiling. You may noticed that I didn''t fix all the typecheck typemaps. I suppose I should fix all of them, but they don''t cause problems with the compilation. This also has a patch to convert void *''s into ruby numbers. This fixes a problem with the get_handle call. I still am not sure what''s

Hi This is a very small patch that seems to solve that "Exit the app and get a segfault in return" problem. Another thing: bigdemo.rb:395 does item = event.get_item() if item.is_ok but get_item typemaps TreeItemId into a plain integer, so it doesn''t have is_ok method anymore, is there any wxruby2''yish solution to this kind of problem ? A.K. In case

Attached are patches to make the textctrl.rb sample work fully. Note the new %directorargout typemap I added to fix wxWindows calling into SWIG. I don''t know if this can fix all such problems or not. Let me know what you think. I also rubified the sample a little bit more. Also, note that I fix the << operator so the function can be called. I hope I did this right. Roy

These patches (should) give us support for compiling against Ruby 1.9. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

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