[Fxruby-users] FXTreeLists....

[Hugh S. S. E. E. <hg...@dm...>]

Looking at the examples for FXTreeLists, there are some things that
stand out.

Firstly, an item in an FXTreeList is not an FXTreeList, but an
FXTreeItem. This seems contrary to customary computer science
practice where trees and operations on them are defined recursively.
I suspect that knowing why they are designed differently will help
me understand them better, so if this design has positive benefits
I'd be interested in hearing about them.

Secondly, FXTreeLists allow you to add an item below another item,
and supply "data", defined as "user data" with the object.  This
data can be any Ruby object, can it?   The examples of use with
FXTreeList seem to use a pre-constructed data structure in parallal
with the FXTreeList, but this would seem to suggest I can use the
FXTreeList to structure auxilliary data if I wish, without having to
have two data structures to keep in synch.  Is that correct?

Thirdly, once I start manipulating the data held in each FXTreeItem,
if I wish to expand items below it for example, FXTreeItem doesn't
seem to have a reference to its tree, only its immediate parent, but
modifications to the tree structure don't take place at that level.
how is this sort of thing normally handled?

        Thank you,
        Hugh