search for: zautodefine

...2 HEAD I''ve been having some issues with wxruby when I use the latest and greatest VC++ where not all of the class initializers seem to run. The library will load fine, but Point or Colour won''t exist. I *think* I''ve tracked it to the number of duplicate classes named ZAutoDefine (no class name) which are a hold-over of the pre t-file system. I suspect when wxruby loads, only one of these classes are kicked off due to the fact that they share the same name. Has anybody else seen this behaviour? Thanks, Nick

Sorry things have gone silent on the release front, but I have some good news: I''ve gotten wxruby-swig to build as a OS X framework. This has a couple of ramifications 1) wxruby for the Mac will finally exactly like its Linux and PC counterparts, menu bar and all. 2) Bundling wxruby applications becomes a lot easier. 3) The next binary installer should be able to support darwinports,