I find it very strange that the setVisible method made OOo terminate. The exception afterwards is nothing special, it's just the logical consequence (if there is no OOo process anymore the initiated UNO Runime environment extinguishes as well of course, thus the DisposedException).
So it seems to me, in the case you can reproduce this behavior, that this is a bug. 2006/2/22, Bernhard Donaubauer <[EMAIL PROTECTED]>: > Can I make OO2 to behave like OO1? Can I make OO invisible by API calls? > I tried to cast my desktop object to XFrame and called > > ooDesktop.getXFrame().getComponentWindow().setVisible(false); > > but this ended OO instead of making it invisible and my next API call gets > this exception: > > Exception in thread "AWT-EventQueue-0" com.sun.star.lang.DisposedException: > java_remote_bridge > [EMAIL PROTECTED] is > disposed -- Best Regards Christian Junker --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
