>Hi Agnes
>
>>Looks like somebody is mixed with the differnce betweeen a class and an object ..
>
>Yep. I think they have missed implications of OOP.

I think that we're walking on a thin line between overriding and adding methods in a member object on a form or a container class. While we can do the former, doing the latter is just across the line, and spoils the interface. A subclass can have new properties and methods that its parent class doesn't; an object belonging to a class may have some of these overridden when it appears as a member somewhere, but the trouble here is that the addmethod() allows it to look like it may get new methods - while it actually can't, or simply can't keep them.

IMO, the only thing to fix is that addmethod() should throw an error when applied to anything else but the class being edited. It should not allow to do what isn't available from the form/class popup. The way it is now, it's misleading.