>
>One problem, though, remains. I suppose you determine the current object with ASELOBJ(). But the method window must not match the currently selected object. Some more information can be received from the title, that's what SuperClass from Ken Levy is using. But the problem starts when the current object doesn't match the one in the method window and you have several objects with the same name. There are some techniques you can use to figure out which object is actually meant, but there's no 100% secure way to figure out to which object a method window really belongs.
>
>Anyway, your tool sounds really usefull. Do you plan to load it into the library when you're done? If you need a beta tester... :)
>
>Christof

Excellent suggestions. And yes I had to plunder Ken Levy's superclass code to get the information I wanted. If I have the time I might be able to solve the above mentioned problem I'll send you the code snippet.