search for: evt_xxx

...t; %import "include/wxObject.h" </span><del>- </del><span class="cx"> %include "include/wxEvtHandler.h" </span><span class="cx"> </span><del>-%{ </del><ins>+// The EvtHandler instance event methods (evt_xxx) are not defined +// here. Instead, they are defined by Events.cpp, generated from +// swig/Event.i and modified by swig/fixevents.rb </ins><span class="cx"> </span><ins>+// This provides the public Ruby ''connect'' method +%extend wxEvtHandler { +...

...uestions regarding wxSugar: 1. I only find one sample application for wxSugar, but as I understand from the docs, wsSugar is the preferred approach. Are there any more wxSugar samples available somewhere? 2. When I run sugar-sample.rb, I get a couple of warnings: "listen is deprecated, use evt_xxx directly". Just wanted to check: Is this sample outdated or is there some version mismatch? 3. Again when using sugar-sample.rb, the bottom part of the list box is covered by the panel with the buttons/dropdown/edit controls. I have to stretch the window quite much to get all the list box...

...## </del><span class="cx"> </span><del>- - </del><span class="cx"> %{ </span><ins>+ +// TODO - there is considerable duplication between the public ruby +// ''connect'' method and internal_connect - in fact all the evt_xxx +// methods could now be implemented in ruby via ''connect'' +// Internal method that links a ruby Proc (the block passed to evt_xxx) +// to the WxWidgets C++ event handler method. </ins><span class="cx"> extern swig_class cWxEvtHandler; </span><ins&gt...

...d to identify which widget''s events are being listened for (as with CommandEvents like evt_button), it''s assumed that if a Wx::Window is passed, we want its id. Code that does this is already in wxSugar - event_connector, but I think it would be better to build on the existing evt_xxx syntax than introduce a new syntax. This doesn''t break backward compatibility, and isn''t "magic". 2) ''each'' for list-like classes This one I''m less bothered about, but I fairly often want to loop over a control with multiple items (eg Choi...

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

...ense -%include "common.i" - -%module wxEvents; - -// This module defines all the EVT_ constants that uniquely identify -// each type of GUI event that WxWidgets can generate. -// -// SWIG''s output of this file is post-processed by swig/fixevents.rb in -// order to define a set of evt_xxx methods that all classes inheriting -// from EvtHandler should hae, in order to define event handlers in -// Ruby. -// -// To wrap a type of wx event that is missing: -// 1) Create a .i file to wrap the Event class -// 2) Add the appropriate EVT constants to this file -// 3) Add the mappings from...

Hi! Is it possible to somehow eliminate the use of the self.get_id''s in most situations? When you set up an event, you always must type sg. like evt_tree_key_down(self.get_id) {|e| where self.get_id can be the default or something... Gergo -- +-[ Kontra, Gergely<kgergely@mcl.hu> PhD student Room IB113 ]---------+ | http://www.mcl.hu/~kgergely "Olyan langesz

Hi, 1) Can the online api docs get updated? Specifically can the overview pages get added in to the main http://wxruby.rubyforge.org/doc/ index.html page? I happened upon the link to the Event Overview page while browsing some class and wished that it had been listed in the Event section of the index page.I don''t know how many other "overview" pages there are but it

Hi Please find attached a set of patches and swig files to implement Wizards for wxruby. Also a brief sample. Quick q - the C declarations of evt_xxx_xxx methods and their attaching to Ruby classes seems to be duplicated across Events.i and EvtHandler.i - is one of these the right place to be adding them? or both? Thanks alex _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://r...

Hi I''m pleased to announce the release of wxruby2 version 1.9.0. This is a significant milestone for wxruby as this is the first release that we consider near to production quality. We hope that this 1.9.x series of releases will soon lead to a stable wxruby 2.0. = INSTALLATION The easiest way to install is using a ready-to-use binary gem for your platform: gem install wxruby Or

...d>1068</dd> <dt>Author</dt> <dd>brokentoy</dd> <dt>Date</dt> <dd>2007-06-25 14:37:07 -0400 (Mon, 25 Jun 2007)</dd> </dl> <h3>Log Message</h3> <pre>Ensure evthandler.rb is loaded before other classes which might modify evt_xxx methods</pre> <h3>Modified Paths</h3> <ul> <li><a href="#trunkwxruby2libwxrb">trunk/wxruby2/lib/wx.rb</a></li> </ul> </div> <div id="patch"> <h3>Diff</h3> <a id="trunkwxruby2libwxrb">...

...<span class="cx"> </span><span class="cx"> class Wx::EvtHandler </span><del>- </del><ins>+ # Given a Wx EventType id (eg Wx::EVT_MENU), returns a WxRuby Event + # class which should be passed to event handler blocks. The actual + # EVT_XXX constants themselves are in the compiled library, defined in + # swig/classes/Event.i </ins><span class="cx"> def self.event_class_for_type(id) </span><span class="cx"> if evt_klass = EVENT_TYPE_MAPPING[id] </span><span class="cx&quot...

...hat returns an object (rather </span><span class="cx"> than an object reference or pointer) is currently </span><span class="cx"> being removed by swig. ARGH! </span><span class="cx"> </span><del>-- Add support for evt_xxx(:method) as an alternative - -- Remove debugging output for director constructors/destructors - </del><span class="cx"> - Add aliases like label and label= for get_label and set_label. Patch </span><span class="cx"> submitted, decide later whether to a...

I am trying to use a grid widget in my application, but run into a number of issues: -- Can they be placed in a panel? Or better yet, placed in sizer with other controls? I have only been able to place a grid inside a frame. -- Can you designate multiple rows (or columns) as being used for labels? -- Can you create cells that span cols (or rows)? -- What events are available to trigger on? How

...- VALUE m_func; </del><ins>+ + VALUE m_func; </ins><span class="cx"> }; </span><span class="cx"> </span><del>- </del><ins>+// Internal method that links a ruby Proc (the block passed to evt_xxx) +// to the WxWidgets C++ event handler method. </ins><span class="cx"> void internal_connect(VALUE self, int firstId, int lastId, </span><span class="cx"> wxEventType eventType) </span><span class="cx"> { </span&...

...<span class="cx"> </span><ins>+// This module defines all the EVT_ constants that uniquely identify +// each type of GUI event that WxWidgets can generate. +// +// SWIG''s output of this file is post-processed by swig/fixevents.rb in +// order to define a set of evt_xxx methods that all classes inheriting +// from EvtHandler should hae, in order to define event handlers in +// Ruby. +// +// To wrap a type of wx event that is missing: +// 1) Create a .i file to wrap the Event class +// 2) Add the appropriate EVT constants to this file +// 3) Add the mappings from...

...p&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp2006-12-31 04:04:00 UTC (rev 814) </span><span class="lines">@@ -1,3 +1,13 @@ </span><ins>+# This describes the event types known to wxRuby. It is used by +# swig/fixevents.rb to automatically generate a set of evt_xxx methods +# for binding events +# +# In each array: +# * the first item is the name of the method that will be created +# * the second item is the number of parameters the method expects +# * the third item is the mapping to an wx event type constant +# (see RubyEventTypes.i) + </ins><sp...

...> </span><span class="cx"> %} </span><span class="cx"> </span><del>-%init %{ -extern void Init_wxRubyEventTypes(); - -Init_wxRubyEventTypes(); -%} - - </del><span class="cx"> // The EvtHandler instance event methods (evt_xxx) are not defined </span><span class="cx"> // here. Instead, they are defined by Events.cpp, generated from </span><span class="cx"> // swig/Event.i and modified by swig/fixevents.rb </span></span></pre></div> <a id="trunkwx...

...ivate", VALUEFUNC(evt_activate), -1); -&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsprb_define_method(cWxEvtHandler.klass, "evt_activate_app", VALUEFUNC(evt_activate_app), -1); - -%} - -#endif </del><ins>+// The EvtHandler instance event methods (evt_xxx) are not defined +// here. Instead, they are defined by Events.cpp, generated from +// swig/Event.i and modified by swig/fixevents.rb </ins></span></pre> </div> </div> </body> </html>