This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Inside a ModuleInstall.restored() method, I'm calling LifecycleManager.exit() to shutdown my application after a failed log on. When I shutdown the app this way, the next time I start the application (i.e. whith a correct login) the following happen: a) The app *works* i.e. it's not frozen. b) The main window has a very small size, and shows on the top left corner of the screen. c) The main window's layout is broken, with TC's appearing anywhere. d) If I close all TCs, everything is back to normal. Of course, after a normal shutdown, everything is ok. Is there any way I can avoid this broken-layout-start after a forced shutdown from a restored() method? ----- Gustavo.
Note that using a WindowListener on the MainWindow, as suggested by some people on the list, it's possible to shutdown without breaking layout. I don't know if this is the "right" way. ----- Gustavo.
As suggested by Rich Unger, I've tried to call Lifecycle.exit() from ModuleInstall.validate(), instead of ModuleInstall.restored(). This doesn't break the main window's layout, and this way I can avoid the flashing caused by the main window appearing and disappearing when using the WindowListener approach. But validate() gets called earlier on the startup process, and some things don't work as expected, i.e. my dialog doesn't have the app's look and feel. I've noted some keyboard focus problems too. ----- Gustavo.
gustavo, pls see issue #67934, the new api might solve your problem i think
I've tested the new API on a 6.0 daily build and it works. I'm new to issue tracker, should we mark this issue as FIXED, being under 5.0? ----- Gustavo.
I'm marking this as fixed and dependent on 67934, as the problem was solved by using solution in 67934.