At this point we branch off into a discussion of project and class design. Have you read Drew's discussion of why you should never use his composite classes? It's exactly for the reason you're discussing below - you're not sure of the exact parent/grandparent/... hierarchy.

When you subclass a control, ESPECIALLY a composite control, you have to be aware of the hierarchy and whether it will affect you later. If you can't see it in SuperCls your hierarchy has branched somewhere and you may not have access to the code.

I agree the utility would be a neat piece of code, though.

Barbara

>Yes we are. This is excellent for walking back through super classes, but once the classes start branching to other methods it can get a little messy. It would be great to have a utility that would build a tree of the entire branch so you could see at a glance the entire scope of an event.