In the meanwhile, could you try the proposed patch and see if it works
as expected?
Thanks for the fast turn-around, and that fixes it completely!
I am new to this mailing list, do you send out notifications of all
bug fixes and changes to CustomTreeCtrl? I searched previous
mailings and found two fixes, one for tooltips and one for using
the keyboard to traverse the tree and added those both in, but
I want to make sure I don't miss anything in the future. Or if
you are making these changes to the CVS I could pull it from there,
wherever it is.
P.S. Thanks for all your hard work, this is an amazing addition
to wx!!!
this is the latest patch for CustomTreeCtrl, which includes the
fix for the bug uncovered by Mike (wrong GetSelections with
wx.TR_MULTIPLE or wx.TR_EXTENDED), plus the substitution of all the
lines which trown the deprecation warning about raising a string
exception.
The patch is rather long, but only because I had to substitute
millions of "raise something" with "raise Exception(something)".
The patch has been created against wxPython CVS.
As usual, if you find any bug or suspect behavior, please report it!
On 12/20/06, Andrea Gavana <andrea.gavana@gmail.com> wrote:
Hi Mike,
> Thanks for the fast turn-around, and that fixes it completely!
I am glad it works
> I am new to this mailing list, do you send out notifications of all
> bug fixes and changes to CustomTreeCtrl?
Well, it depends: usually, the accepted strategy when someone finds a bug is:
1) Fix it (if possible);
2) Make a patch against CVS (and possibly send the patch through the
mailing list);
3) Send the patch to Robin;
4) For the official implementation, wait for the next wxPython
release. Robin is very fast in putting things together and the
wxPython mailing list is the most friendly and active forum I have
ever seen.
> I searched previous mailings and found two fixes, one for tooltips and one for
> using the keyboard to traverse the tree and added those both in, but
> I want to make sure I don't miss anything in the future. Or if
> you are making these changes to the CVS I could pull it from there,
> wherever it is.
I have no write access to CVS, so I just send patches to the mailing
list and to Robin when needed. In any case, if you are using 2.8.0.1,
those 2 previous patches plus the current one are ok, you are using
the most updated CustomTreeCtrl version on earth
For the official one, we'll wait for wxPython 2.8.0.2 (or 2.8.1?).
> P.S. Thanks for all your hard work, this is an amazing addition
> to wx!!!
Some of these controls have been added to wxPython (namely
FoldPanelBar, HyperLinkCtrl, CustomTreeCtrl, ButtonPanel,
FlatNotebook), so anyone that plans to use them should use the wx.lib
version. For the others, feel free to download them, to play with them
and possibly to report bugs and misbehaviors.
this is the latest patch for CustomTreeCtrl, which includes the
fix for the bug uncovered by Mike (wrong GetSelections with
wx.TR_MULTIPLE or wx.TR_EXTENDED), plus the substitution of all the
lines which trown the deprecation warning about raising a string
exception.
The patch is rather long, but only because I had to substitute
millions of "raise something" with "raise Exception(something)".
The patch has been created against wxPython CVS.
Thanks, I've applied the patch and will check it in later today.
BTW, if you want people to be able to catch any of the exceptions raised by this module then you may want to consider using a derived exception class. Since Exception is the base class using a try:... except Exception:... will result in all types of exceptions being caught. That could result in legitimate programming errors being hidden.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
