Just wondering, why doesn't FLTK provide access to a global widget tree? Behind the scenes, does FLTK not use a tree like structure to represent the relationship between widgets, in  a fashion similar to HTML?

A simple widget tree for an FLTK app might look like: 

________________________________

        Window

            /     \

    Group     Group 

       /\                 \

Button Button   Button

________________________________

Wouldn't it be great to have access to the FL_Tree functions like root(), insert_above(), set_root(), prev(), next(), etc for all of our widgets?

For example,  what if we wanted to make a Photoshop-style layer panel, a UI feature well suited to represent widgets in a tree data structure:

          Container

            /    \

       Layer    Group

                       /  \

                   Layer  Layer

As things stand, we have to wrap widgets inside of a custom tree structure that we provide. But if behind the scenes FLTK already has some kind of tree like representation of widgets, why not let users leverage this?

    

--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/b93d7d20-db4e-4695-8898-aa2bb73a8b02n%40googlegroups.com.