I love the new wxTreeListCtrl, but I ran into a few, bugs?
First of all, the HitTest and other methods like GetFirstChild throw the
following error.
val1, val2, val3 = self.HitTest( event.GetPosition() )
File "/usr/lib/python2.2/site-packages/wxPython/gizmos.py", line 663,
in HitTest
val1, val2, val3 = controls2c.wxTreeCtrl_HitTest(self, *_args,
**_kwargs)
TypeError: Type error in argument 1 of wxTreeCtrl_HitTest. Expected
_wxPyTreeCtrl_p.
I assume this is some identity issue with the wrapper. Is there a way to
find the wxTreeCtrl within and somehow call these methods on it? Or am I
off on this one?
Also, EVT_RIGHT_UP and other similar events are not firing up. I had to
pass wxTreeListCtrl.GetMaitWindow - a wxScrolledWindow - to the macro.
So should I be doing things differently or are these real bugs?
I love the new wxTreeListCtrl, but I ran into a few, bugs?
First of all, the HitTest and other methods like GetFirstChild throw the
following error.
val1, val2, val3 = self.HitTest( event.GetPosition() )
File "/usr/lib/python2.2/site-packages/wxPython/gizmos.py", line 663,
in HitTest
val1, val2, val3 = controls2c.wxTreeCtrl_HitTest(self, *_args,
**_kwargs)
TypeError: Type error in argument 1 of wxTreeCtrl_HitTest. Expected
_wxPyTreeCtrl_p.
I assume this is some identity issue with the wrapper. Is there a way to
find the wxTreeCtrl within and somehow call these methods on it? Or am I
off on this one?
Also, EVT_RIGHT_UP and other similar events are not firing up. I had to
pass wxTreeListCtrl.GetMaitWindow - a wxScrolledWindow - to the macro.
So should I be doing things differently or are these real bugs?
They are real bugs that I just fixed about 24 hours ago. You can fix the gizmos.py file with these changes: