Type hierarchies have always described the ancestry of a selected class. I actually can't think of any class viewers offhand that show derived classes unless they're full-project analysis tools. (It would kinda get out of control anyway, look at QWidget!)
Fact is, you can always draw an ancestry diagram because all of the relevant classes MUST be fully-defined in the scope. The descendants could be anywhere -- there's no link from a superclass to the subclasses, not in code, not in the binary. QObject has documented subclasses that aren't even defined in the same library. /s/ Adam On Wed, Feb 9, 2011 at 5:06 PM, Stephen Chu <[email protected]> wrote: > Am I doing it wrong or the "type hierarchy" works the opposite way a > class viewer typically works? I was expecting it show some sort of tree > view of a given class with it's parent class and all derived classes. > Something like this: <http://i.imgur.com/zY5Oj.png> > > What I get is just the selected class and its ancestors. None of its > derived classes is included. Is there anyway to make it so I can see > both ancestors and descendants? > > Thanks. > > -- > Stephen Chu > <mailto:[email protected]> > <http://www.ju-ju.com> > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.qt.nokia.com/mailman/listinfo/qt-creator > _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-creator
