similar to: Patch to wxWindow.h

Attached is a patch file for listbook.rb 1) Message box scrolls properly now 2) Blank lines are skipped when adding pizzas and ice cream _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

Hi, I am making a game with Ruby/SDL and have run into trouble finding a GUI to cooperate. I have seen numerous examples of wxWindows in combination with SDL (wxPython and PyGame), but have yet to be able to do it in ruby (PyGame example: http://wiki.wxpython.org/index.cgi/IntegratingPyGame). I am not very good with wxRuby as this is my first time using it and thought some more knowledgable users

About a year ago (ouch!), Robert Carlin submitted a ported version of the wxPython demo/sample. I hoped to include it in wxruby2, but it relies on SplitterWindow, which isn''t in wxruby2 yet. I tried to implement SplitterWindow myself, but got such strange results that I''m thinking I did something wrong. Even though the generated C++ code specified a variable number of

I feel like I''ve mostly been banging my head against header file issues for the last couple weeks. I don''t feel like I''ve gotten any actual ''work'' done on fixing wrapping problems, adding new classes or improving the samples. I''m searching for any but haven''t found ''em. Some things I''ve noticed: 1) Some

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

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''ve downloaded wxPython and the demos and am trying to update our bigdemo. I can see some big differences in how wxRuby and wxPython interact on Windows. Our layout seems wrong. For example, I never knew the textctrl sample had more than two controls on it! I only ever saw the two. In the python version, the controls lay out close together. Secondly, on the ComboBox sample

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.

Hopefully a good listbook.rb patch _______________________________________________ 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

These patches implement wxRegion and the ShapedWindow sample. I stole the ruby image from ruby-lang.org. Shamelessly. Maybe someone has a better image we can use for the shaped window. It didn''t seem to make sense to use the Python image. I''d like something even bigger than what I stol^h^h^h^hmade, preferably. Image goes in icons. I had to %ignore one function in wxRegion.

I have basically spent a full day''s worth of time I could have spent working on something productive trying to figure out which function signature I changed that is causing wxRuby to crash. It just takes so long to recompile this from scratch and without dependencies you kind of have to when you change wxWindow.h. I updated a lot of signatures to match the wxWindows header file.

I added the Listbook class (basically the same as the Notebook class with some name changes). I also took the time to write a sample that uses it. The sample interface uses XRC and is slightly more advanced than the current XRC sample. Sean _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org

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());

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

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

This patch file will allow the MDI example to run. We''ll need to revisit it later. There''s still a crash but it''s the same crash as from the scrolled window example. I''ll send a patch later that fixes the problem with DrawLines. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org

In the dialogs.rb sample, when you click the delete button you get: C:/RubyDev/wxruby2/samples/dialogs/dialogs.rb:61:in `onButton'': undefined method `free'' for #<Wxruby2::Button:0x36474b8> (NoMethodError) Should all/some wxObjects have a free function? how do we intend to handle this?

The previous TreeCtrl.i was very messy and just plain wrong, for instance it had GetFirstChild as depreciated when in fact only 1 version of it was depreciated not both. I changed GetFirstChild and GetNextChild to return an array of values to match the wxPython and wxPerl usage. I also noticed that wxTreeCtrl is inherited from wxControl on Windows and wxScrolledWindow on everything else so I #if

These files add the virtual function AcceptFocus that was missing from wxWindow.h. In order to make things right I had to make sure it was also declared in all the places where wxWindows also changes it. Also, in wxTextCtrl on Windows GetDefaultAttributes needs to be redeclared. I haven''t downloaded the Unix and Mac headers for 2.6.3 so I couldn''t see if it also applies