similar to: Patch to RubyConstants.i

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

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

This patch fixes up two problems with ArtProvider constants and fixes a small typo. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

Here''s my first try at a contribution to the wxRuby project: The tree control seemed to lack a more Ruby-ish way to add a bulk of items to a tree control (and to easily connect a data structure to a tree). Since tree view can be seen as an array of arrays, I simply added a method called append_array (see attached file). With it, you can add a full tree as simple as: --- root =

I have been playing around with the wxRuby TreeCtrl for a couple of weeks now and I can''t figure out how to get the scrolling to work. I believe it has scrolling built in but I can''t get the to show up. I can place the TreeCtrl in a ScrolledWindow and scroll around over the tree but that breaks TreeItem visibility checks because the TreeCtrl doesn''t know about

The attached fixes set_item_data, get_item_data and some other methods for the TreeCtrl so they work nicely with Ruby objects and GC. In C++ Wx TreeCtrl item_data works differently from client_data in classes derived from ControlWithItems (eg Choice, ListCtrl). A one-to-one mapping of the way TreeCtrl works would mean that you would have to derive a class from TreeItemData, and instantiate

See the attached patch to typedefs.i. I added the enums included from CalendarCtrl.i. The calendar sample won''t work correctly without this patch but I''m wondering if there''s a better way, such as moving the declarations into RubyConstants.i instead. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org

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

Hello all. This gets past the problem in bigdemo where it won''t start the application at all. That was where it was overflowing the stack on get_label. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

Hi folks A couple of questions: 1) I seem to get funny artifacts in the display of TreeCtrl, ComboBox and ListBox when the MDI child frame containing it is first painted (see attached - it should be two-root treeview, unopened). I''m not sure if it''s related to being in a MDI, but the controls sample looks OK. The artifacts are cleared up when it''s repainted or

Here is a small patch to apply the above RubyConstants.i, it makes it so all the samples run. Run the patch in the same directory as the RubyConstants.i Sean On 8/30/05, Sean Long <sean.m.long@gmail.com> wrote: > I went through RubyConstants.i and updated it so everything matches > wx2.6.1, I also did some rearranging so it is easy to see which files > the different constants came

Hi! I discovered WxRuby2 and WxSugar a short while ago (1.9.1) and I really like its professional look and the platform independance. But especially the simplification and ''rubyfication'' that you already achieved and are planning for 1.9.2 (event handlers) is funstuff! Thanks a lot! And with Ruby 1.9/2 the keyword constructors will be even nicer with the new hash syntax:

- Added wxDefaultCoord - Updated the standard IDs so they match the 2.6.3 headers which adds wxID_NONE. Sean _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

While investigating the ''TextCtrl background?'' message from Mark I noticed some Constants related to TextCtrl were missing. Sean _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

Given the following hash: #... @project_list = { ''Contract0'' => nil, ''Contract1'' => { ''Project1'' => nil, ''Project2'' => nil, ''Project3'' => { ''task1'' =>

Hi I''d like to tag and release 0.0.38 in the next week or so. I know we still have a nasty GC bug on windows, but I''m thinking we could just tell people to use GC.disable for the time being if that avoids the problem. After all, it''s not meant for production use yet. This would make other recent bugfixes and enhancements available. Plus having a binary build out

Hi, The documentation mentions the evt_tree_item_menu method for TreeCtrl but it seems that this method is not defined (wxRuby 1.9.4 on Windows). As a workaround, I''m currently using evt_tree_item_right_click. Cheers. Chauk-Mean.

when can publish the next version? i am waiting... _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

If wxRuby-SWIG is as usable as wxRuby 0.6.0, maybe it should be given a version number and packaged up for download. Given the nature of SWIG, having a lot more people use it would probably result in more code contributions to this project. Seems most of the changes are 2+ months old, so I''m guessing wxRuby-SWIG is fairly stable right now in terms of frequency of changes...

What I''d like to be able to do is use a wxTreeCtrl to manage a tree layout of not only text, but several buttons which would line up adjacent to the text in the tree items. I''ve googled around a bit on this and it doesn''t seem straightforward, if it is possible at all. Can anyone provide any pointers for attempting this? In a simple ASCI schematic, it would be like