Re: [dba-users] Now that it stays open, how will we kill it (redaux)

[Andrew Jensen]

Frank Schönheit - Sun Microsystems Germany wrote: Hi Andrew, As a workaround, try opening the form a second time, this should simply raise the respective frame, and return the respective form document component, which you can close then. Do you think this is feasible? I tried that that in in the past, to no avail. But I haven't tired it in RC2, as my solution of closing the frame is working for now. Hmm, it should work. What does "to no avail" mean? No component returned? A second instance loaded? Component not closable? "to no avail". I opened the form a second time, a component is returned, only one instance of the form on screen is possible, and closing this newly rturned component is no diferent then doing the same to the earlier reference to it. (that is what I meant). As I said I don;t know if this changed in RC2, I have not yet been able to get RC2 to be stable and reverted to RC1. I guess it is my system as others don't seem to be having the same problem. API-wise, a quick solution would be to support a respective command in the |execute| method. A better solution would probably care for future requirements such as opening a form multiple times - if you do so, a simple formDef.close cannot decide which instance to close. Hmm, not sure at the moment. So does that mean that we will be able to open mulitple insances of a form in 2.0.1 ? :-) Hey, "future" is a long time frame, isn't it? :) Seriously, don't expect this in 2.0.1. Features as this don't usually go into micro updates. Sometimes there is a difference between what the Left side of the brain knows, and what the right side wants. Ciao Frank