similar to: Menu.i.patch

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

The following two patches (theoretically) tell Ruby that it no longer owns menu items after they have been attached to a frame. We''ll need several more of these DISOWN typemaps as we get further into this. _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

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

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

I''m using my SpaceMonkeys game as a testbed to try to get rid of crashing problems. Earlier today, it would crash for me almost immediately, every time. Now, I was able to get about 50 turns into the game! I mentioned the first big change in a different email. The new change I just checked in was to add the DISOWN flag to Window#set_sizer. This is the first time (that I know of) that we

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

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

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.

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.

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

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.

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?

I am trying to use /etc/libvirt/hooks/qemu to control the startup of several guests with interdependencies. The goal is to delay the start of guest B until the DNS server on guest A is running. To accomplish this, I wrote a qemu hook script that detects the normal startup of guest B and start a second script in the background to wait until the preconditions to start B are fulfilled, then start B

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

I''m trying to un-ignore TextCtrl#get_selection. The typemaps work fine, but in the process it breaks get_insertion_point. This is because (on Mac, tho not GTK), get_insertion_point calls get_selection internally and simply returns the first value. I think the return value is being converted from a long to a ruby int twice, because when get_selection is wrapped, it works fine but 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());

Hi guys! I have a question (or a request?) on Wx::ListCtrl#get_item method. As you can see in the wxWindows reference, wxListCtrl::GetItem method of C++ is different from that of wxPython. C++ return value: boolean argument: wxListItem& info wxPython return value: wxListItem arguments: int ID, int column (optional) How about wxruby? >From the wxruby source code, wxruby looks

Hi, I have an interface from R to the wxPython GUI toolkit which works under Windows: http://bioinf.wehi.edu.au/folders/james/wxPython/ (as long as you build RSPython with a shared (not static) Python library). But on Linux I get an error: > library(RSPython) > importPythonModule("wx") Error in .PythonEval(cmd) : Error in Python call:

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