similar to: Free

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

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

Hey Kevin, Am I correct in assuming that if I want a particular widget to respond to an event which doesn''t take an ID as an argument (like evt_size or evt_left_down), that I have to inherit a new widget and define the event handler within the inherited class? Here''s a little contrived code example to illustrate what I mean: class MyCtrl < Wx::TextCtrl def

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

This patch fixes the sample so it works correctly. You''ll need to patches in the previous e-mail. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

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

This fixes truncated text on the CheckListBox sample in bigdemo. 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

Hi Attached, patches to implement ListItem. This class, in wxruby 0.6.0, allows styling of individual items in a ListCtrl, via a particularly clunky API. In disambiguating the overloaded ListCtrl#set_item method it introduces one non backwards-compatible change. I''ve followed the WxPython convention as described in the Wx class ref, renaming set_item(index, col, string, imageid) to

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

Robert McGovern wrote: > > Just to let you know Curt the new debug build works perfectly for me ... > well nearly. Thanks for the confirmation. > Trying to run the controls.rbw example generates an error dialog > > "Debug" > > "E:\dev\RubyDev\wx\src\common\ctrlsub.cpp(120): assert > "m_clientDataItemsType == wxClientData_Void" failed: this

Hi all, I am concerned about the version number for our gem. Currently, we have it set to 1.9, indicating that it is "before the upcoming 2.0 release". However, there is nothing in the version number that indicates this is a "preview" "alpha" "buggy" release. The gem version numbering scheme does not allow things like 2.0-pre. It also requires each public

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

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

I think I had to do this to get the tarball to compile on Windows _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

The latest tarball won''t compile on Windows: src/Functions.cpp(582) : error C2664: ''wxLogWarning'' : cannot convert parameter 1 from ''const class wxWCharBuffer'' to ''const char *'' No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called src/Functions.cpp(592) : error

Hi Attached is a patch to add HtmlWindow and some of its friends, including HtmlEasyPrinting. Also a sample. I haven''t tried exposing the parsing and rendering API yet to allow custom tags etc - I just wanted to get basic HTML and the 0.6.0 compatibility classes first. There may well be some quite easy classes left. There''s one ugly kludge to get OnOpeningURL to compile -

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

This patch fixes the problem with the undefined constants. Apologies to Alex as I didn''t apply his patches yet. The fix is to just removed the _C from the end of the ones that won''t compile anymore. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users