Bug #45582 Splash screen hides startup errors (dialog boxes)
Submitted: 18 Jun 2009 7:50 Modified: 31 May 2013 6:51
Reporter: Karsten Wutzke Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.x OS:Any
Assigned to: CPU Architecture:Any
Tags: dialog box, errors, Hidden, splash screen

[18 Jun 2009 7:50] Karsten Wutzke 
Description:
The MySQL Workbench splash screen hides any dialog boxes appearing due to startup errors.

How to repeat:
When using an incompatible version with certain .mwb files, this can get really annoying as it leaves you no other choice but to kill the MySQL Workbench process manually.

Suggested fix:
Two ways:

1. Implement a thread so that the splash window disappears on a click (or maybe after X seconds)

OR

2. Put any dialogs on top of the splash.
[18 Jun 2009 9:53] Valeriy Kravchuk 
Thank you for the problem report. Can you, please, upload such a problematic .mwb file to demonstrate the bug with WB 5.1.13, for example?
[18 Jun 2009 12:32] Karsten Wutzke 
That's not needed. Try opening a newer nwb with an "old" WB. I tried to open a 5.2.1alpha model with WB 5.1.13 RC...
[19 Jun 2009 6:10] Valeriy Kravchuk 
Verified just as described: try to open .mwb saved by 5.2.1 in 5.0.x or 5.1.x. As a workaround, use Alt-Tab to switch to WB window. Then dialog box with error messages goes to front.
[19 Jun 2009 8:19] Axel Schwenke 
This problem is hard to fix, because window order is decided by the GUI framework (one would expect error messages to go to the front anyway). The workaround would be to disable the splash screen completely. The command line option -nologo disables the splash screen.
[19 Jun 2009 9:54] Karsten Wutzke 
Well, it depends... as you said.

In Java this is very easy to do: when displaying the splash window, either

run a new thread that closes the window after X seconds

OR

produce a splash that disappears when clicking the window.

This should be doable with almost any GUI framework.
[31 May 2013 6:51] Philip Olson 
Fixed as of MySQL Workbench 5.2.45, and here's the changelog entry:

Opening a model from a newer version of MySQL Workbench could generate an
error dialog that was hidden behind the splash screen. This made it
difficult to close the splash screen, which meant MySQL Workbench could not be
used. A workaround was to pass in the "-nologo" option at startup.

Thank you for the bug report.