I need to create my own Treebook and so went ahead and used splitter window and a treectrl. In order for this to look right the root has to be hidden. If I use windows, then the only thing that looks right is using the customtreectrl, otherwise there wont be any + buttons next to items that has children in the tree. If I use linux, then TR_HIDE_ROOT doesn’t work on customtreectrl… but it works on the standard TreeCtrl.
Did I hit a bug here? and is there a way to go around it apart from the obvious of checking what system I’m on and take appropriate measures?.
I’ve attached an example. OptionsTree is the standard wx.TreeCtrl and ConfigTree is the customtreectrl… you can switch between the two by commenting the lines out in the frame.
I need to create my own Treebook and so went ahead and used splitter window
and a treectrl. In order for this to look right the root has to be hidden.
If I use windows, then the only thing that looks right is using the
customtreectrl, otherwise there wont be any + buttons next to items that has
children in the tree. If I use linux, then TR_HIDE_ROOT doesn't work on
customtreectrl.. but it works on the standard TreeCtrl.
Did I hit a bug here? and is there a way to go around it apart from the
obvious of checking what system I'm on and take appropriate measures?.
I've attached an example. OptionsTree is the standard wx.TreeCtrl and
ConfigTree is the customtreectrl.. you can switch between the two by
commenting the lines out in the frame.
For the CustomTreeCtrl you need to use the style flags defined in the
customtreectrl module not the standard wx ones (though they mostly
share the same names.) Also the later releases 2.8.10+ (IIRC) the AGW
widgets uses a different parameter for some of the custom styles
(agwStyle instead of style).
For the CustomTreeCtrl you need to use the style flags defined in the
customtreectrl module not the standard wx ones (though they mostly
share the same names.) Also the later releases 2.8.10+ (IIRC) the AGW
widgets uses a different parameter for some of the custom styles
(agwStyle instead of style).
After adding a child to a node. Not a 100% sure why this is necessary
it seems that it should happen automatically when a child is added to
a node. Would think this would only be necessary when virtualizing the
tree.