>The way the class browser is designed, it will only show the method or property where it was first defined, even if code was added in a child.
>
>Really nothing to get confused about. It is just to understand that that was the logic that was chosen when the tool was made and accept that that is how it is.
>
>I agree that the logic you state could have been applied. That is, show the method where code was added. But other scenarios are possible as well. If the method was implemented in several layers, do we display it in all layers? What about if the method is defined in the parent but left blank. Should the method show in the parent? What about showing all the methods in the child even if there is no implementation in the child? After all, they are accessible from the child.
>
>Just thinking of all the possibilites here makes ME confused, and I am kind of happy with the way it works right now.
>

You might want to look at Ken Levy's SuperCls, which does permit you to drill back to reach code inherited from further up the inheritance chain; it's an add-in to the Class Browser, and like everything Ken does, it's free, and the source is available for it.