Generally, I avoid to be involved in theoretical discussions. What I actually said, that in modeless interface user can pass an object (form), then revisit this object (you understand what I mean) and try to release it, and another object which received the reference already can get into troubles (or whole app will get into troubles?). I don't know, it's too late :). Once again, I am off theory.

>Interesting comment, Edward. I don't pretend to having anything but a remedial understanding of OOP standards...but personally I would think that passing objects (including forms) when something needs to be done would fall under the category of encapsulation. I suppose I'll have remain abnormal < s >.
>
>>Michelle, the normal way of reference any form is to keep OO application hierarchy, i.e. any form can be referenced from higher level object, up to application object. Passing objects to functions is mostly workaround and may not work nicely for modeless interface (surely, shortcut menu is not exactly modeless).