search for: wxperl

...e doc patch reflects this. This means the whole TreeItemData class is not exposed at all in Ruby. I think this is the right way to go, but let me know if it sounds wrong and there''s situations where Ruby code might want this. This is similar to, but not the same as the way wxPython and wxPerl deal with this. I''m going to go back to the other ControlWithItems classes and add item_data support to them along the model of wxChoice. I think it is weird that methods that get data from an item in these classes are called get_CLIENT_data, and now the way they work will be consisten...

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 defined the .i and .h file accordingly. I also added a .i and .h file for the class wxTreeItemId. The TreeCtrl files were changed so much that I am just uploading the who...

...39;t yet researched how hard it would be to do something better. I would love to reuse wx/SWIG files from other projects. However, wxPython appears to use highly-customized swig files. So far I have not seen any that would be usable in wxRuby without a ton of work. That also seems to be true of wxPerl, wxBasic, wxLua, and the other seven bindings for various languages. One of my design goals is to end up with a set of class declarations that could be used by a new wx/SWIG project without much effort. That''s all for now. If you have any ideas for how we can obtain or generate swig f...

...sp*/ - </del><span class="cx"> void CentreOnScreen(int direction = wxBOTH) ; </span><del>- -&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp/** -&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp * \brief \perlnote{In wxPerl this method returns a 2-element list instead of -modifying its parameters.} -&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp * \param int* -&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp * \param int* -&nbsp&nbsp&nbsp&nbsp&am...

Hi Curt/all, Would it be a bad idea to bug Julian again to add us here? http://www.wxwindows.org/contrib2.htm We are already in the Community pages, but wxPerl/wxPython/wxLua/etc are also on the Contributions page. -- dave

Hi guys! I have a question (or a request?) on Wx::ListCtrl#get_item method. As you can see in the wxWindows reference, wxListCtrl::GetItem method of C++ is different from that of wxPython. C++ return value: boolean argument: wxListItem& info wxPython return value: wxListItem arguments: int ID, int column (optional) How about wxruby? >From the wxruby source code, wxruby looks

...p&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp//Change signature so it returns an array of the TreeItemId and the Cookie. </span><span class="cx"> &nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp//This behavior matches that used by wxPython and wxPerl. </span></span></pre> </div> </div> </body> </html>

...p&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp//Change signature so it returns an array of the TreeItemId and the Cookie. </span><span class="cx"> &nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp//This behavior matches that used by wxPython and wxPerl. </span><span class="cx"> &nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbspVALUE get_first_child(const wxTreeItemId& item) </span></span></pre> </div> </div> </body> </html>

Swig''s bad interface generation strikes again. get_text_extent called with 1 argument maps to WindowDC''s _wrap_wxWindowDC_GetTextExtent__SWIG_0 Since this generates a wxFont that''s not initialized to nil it fails when calling into wxWindows. Anyone have a suggestion?

Hi We''re all keen to get a release out, for lots of reasons: getting more people testing, showing people the progress we''ve made, etc. So I suggest that we now look to release an alpha version very soon, based pretty much on the current state of CVS plus pending check-ins. Sure, it has some bugs, some missing features and segfaults occasionally - but my experience on OS X

We''ve had some discussion in the past about the wxruby vs wxruby-swig name, and how they are a bit confusing. My big problem with ''wxruby-swig'' is that unless you know what ''swig'' is, it''s not a terribly useful (or sexy) postfix. It''s like naming a car after it''s manufacturing process - "the all new Acura

...p&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp//Change signature so it returns an array of the TreeItemId and the Cookie. </span><span class="cx"> &nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp//This behavior matches that used by wxPython and wxPerl. </span><span class="cx"> &nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbspVALUE get_first_child(const wxTreeItemId& item) </span></span></pre> </div> </div> </body> </html>

I have written an addon file for rake that turns the wxWidgets documentation into something much more Ruby like. The code has not been cleaned up or re-factored and needs some extra features added but it does quite a bit already. I have uploaded the generated documentation to my web site so people can view it. http://hailstonesoftware.com/_files/Ruby/wxruby/html/wx_contents.html. I also have a

And I got this lousy LatexParser. Ah well... A new cut of the automatic WxRuby documentation is now viewable online at http://www.pressure.to/wxruby/. There''s also a pdf version http://www.pressure.to/wxruby/wxruby.pdf [3MB, 751 pages!] and a tarball http://www.pressure.to/wxruby/wxruby2.tar.gz [1.3MB] In terms of output, it''s no advance on what Sean has already done.

...the accelerator table from a Windows resource (Windows only). - - - - - - - - - -\pythonnote{The wxPython constructor accepts a list of -wxAcceleratorEntry objects, or 3-tuples consisting of flags, keyCode, -and cmd values like you would construct wxAcceleratorEntry objects with.} - -\perlnote{The wxPerl constructor accepts a list of either - Wx::AcceleratorEntry objects or references to 3-element arrays - ( flags, keyCode, cmd ), like the parameters of Wx::AcceleratorEntry::new.} -&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp * \param const wxString& -&nbsp&...

...amp;nbsp&nbsp&nbsp&nbsp * \brief Adds custom, user-defined language to the database of known languages. This -database is used in conjunction with the first form of - . - -wxLanguageInfo is defined as follows: - - - - - should be greater than wxLANGUAGE_USER_DEFINED. - -\perlnote{In wxPerl Wx::LanguageInfo has only one method:\par -Wx::LanguageInfo-&gt;new( language, canonicalName, WinLang, WinSubLang, Description )} -&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp * \param const wxLanguageInfo& -&nbsp&nbsp&nbsp&nbsp&nbsp&n...