similar to: Windows gem

Hi Seems that the last round of commits makes bigdemo crash fairly quickly. Guessing it''s something to do with either the Window or fixmodule change. Program received signal EXC_BAD_ACCESS, Could not access memory. 0x00034fbc in rb_obj_is_kind_of (obj=3825080, c=1839676) at object.c:523 523 object.c: No such file or directory. Any hints? alex

Hi I''m pleased to let you know that wxruby2-preview 0.0.36 is now available on Rubyforge. Binary gems to follow... To check out a clean copy from SVN and build from source: svn co svn://rubyforge.org/var/svn/wxruby/tags/wxruby2/0.0.36 cd 0.0.36 rake gem WXRUBY_VERSION=0.0.36 From my reading of SVN docs it''s probably wise for developers to checkout anonymously as a bit of

Attached are some patches to implement the TaskBarIcon. Let me know how this works on Linux and OS X. You may want to ''svn update'' first and get the new version of ruby.png since I fixed the transparent background. Roy -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: bigdemo.rb.patch Url:

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

Updated all the sample files to add the shebang line and the require code we discussed. I also added the wxRuby copyright notice to all the samples I know I added (I may have missed some). Next, how about we rename all the .rbw files to .rb and update bigdemo? Roy

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

The files checked out of SVN come out without the ability to be executed. So, I can''t run the samples without prefixing with ''ruby '' Before, the file associations allowed me to run samples just by putting the name on the command line. Can we fix this? Roy

Hi Patches to TreeEvent.i and wxTreeEvent.h to implement missing methods (and fix a crasher in bigdemo along the way) Two of the missing methods appeared just to be down to errors in the header file. The other (get_label) works fine - perh a bug in previous versions of SWIG? Methods tested and return correct values on OS X. I could offer a test addition to bigedemo, but this

This patch file allows the About menu item in the bigdemo sample to work. _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

Here''s a revised patch for fixing get_client_data. It tackles the serious problem with the previous patch (segfault on exit) and makes the key bit of code available for sharing with other ControlWithItems classes. So it''s a candidate for applying. If it works I''ll add to other relevant places, like ListCtrl and ComboBox. The tricky part was detecting whether a

Hi I tagged 0.0.38 and started a release on rubyforge. I''ll do the doc packages & upload plus gems for OS X ppc and Linux; TIA for gems for Windows and OS X Intel - please upload whenever convenient. Once we have a set of binary gems, I suggest we do an announce to wxruby-users and c.l.r, inc explaining this is still alpha, summarising the new features, and that people should

This patch removes the call to ''free'' from the sample. Roy _______________________________________________ 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

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

Hi Now we''ve got the download problems nailed, shall we do an announcement on comp.lang.ruby? I can do it if you''re really busy, but Kevin I think you have first refusal as you''re owed the biggest chunk of kudos for getting us this far. re patch backlog: no worries - just clearing the decks before having another go at integrating wxScintilla - but I can''t

Hi all, How soon can we do our alpha (binary gem) release? 1. I would like to get the samples working a bit better, but am ok simply documenting most of the current problems. Do the samples crash every few minutes for other people? Or is it just me? I would like to have a copyright/license comment at the top of every sample file before the alpha release. 2. I would like to receive and merge a

I will probably be sending patches for about 30 header files. I have put some TODO: notices in some of the header files where I''ve had to temporarily remove some things. How do you guys want these? A .zip of all the changed files? A .zip of all the patches? Individual e-mails? All attached to one? Roy

I cut-n-pasted the public section from the wxWindows headers. Several things were missing so it seemed the easiest way to fix it. This fixed a problem with the way the overloaded new was being handled. This correctly generated all the versions so that it won''t have the problem with the non-initialized default parameters. I will admit I haven''t done serious testing on

Patch to the notebook example to remove the call to the deprecated NotebookSizer. It appears to work just fine without the sizer. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

Hi all Have been taking a look at the samples to see what''s broken. Not looking TOO bad overall, but a few problems we should try and tackle before alpha: Firstly, I have a few commits (minimal, dialogs, unicode) - anyone else been working on these or can I go ahead? One general issue is that many of the samples rely on being run from their own directory, but don''t enforce