Simple enough, I put 2 TreeCtrl(s) into a SplitterWindow.
Though SplitterWindow does not inherit ScrolledWindow, scrollbars still show up as the trees get larger. My question is that, can I capture the events of these scrollbars, or do I have to wrap the trees into 2 ScrolledWindow(s) (which in turn become the subwidgets of the splitter) to do that? If the former is feasible, how?
I noticed that the same thing also happens to frames besides splitters. Do the scrollbars actully belong to the TreeCtrl?
Thanks in advance.
Simple enough, I put 2 TreeCtrl(s) into a SplitterWindow.
Though SplitterWindow does not inherit ScrolledWindow, scrollbars still show up as the trees get larger. My question is that, can I capture the events of these scrollbars, or do I have to wrap the trees into 2 ScrolledWindow(s) (which in turn become the subwidgets of the splitter) to do that? If the former is feasible, how?
I noticed that the same thing also happens to frames besides splitters. Do the scrollbars actully belong to the TreeCtrl?
Yes, the scrollbars are an implementation detail of the wx.TreeCtrl, and are totally managed by the tree. On the platforms where the generic tree widget is used you can probably get access to the scroll events with a little digging, but you will not be able to do that on Windows. If you really need to do this you can use the CustomTreeCtrl instead since it is generic and implemented in Python.
ยทยทยท
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!