Bug #61122 Apply changes window prevents interaction with main window
Submitted: 11 May 2011 1:21 Modified: 1 Sep 2011 15:42
Reporter: Jeremy Bell Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S2 (Serious)
Version:5.2.33/5.2.34 OS:Windows (7 64 bit)
Assigned to: CPU Architecture:Any
Tags: apply changes window, background window, can't click, dialogue window, Stuck

[11 May 2011 1:21] Jeremy Bell
Description:
When applying changes to a large table which takes a long time, and then switching to a different app, and then switching back opens the main Workbench window, and the dialogue windows are not visible, therefore cannot be closed, even when they have finished running their query. The main window cannot be click or even closed normally. Task manager must be used to kill Workbench and start again.

How to repeat:
1. Bring up the ALTER table dialogue for a large table, say 1 million + rows. It needs to be a big enough table that adding an index will cause Workbench to become unresponsive while the query is being run.
2. Add an index on a couple of columns, and click apply, and then apply again on the confirmation window.
3. Quickly change to another window, say your internet browser, and then try switching back to workbench while it's still unresponsive. It should remain unresponsive, and the windows 7 preview feature (the little preview windows that pop up when you mouse over a running windows 7 app in the task bar) should no longer show all three windows (Workbench, Table editor, and confirmation) but should only show workbench.

When you return to workbench it will be unresponsive and the dialogue windows will be stuck behind it. So even when the query finishes and Workbench becomes responsive again, you cannot interact with the main window because the dialogue windows have focus, but cannot be brought to the front.

Suggested fix:
Allow the main workbench window to remain independent from the dialogue windows, so that even when the query is running, the workbench window is always available to be used. This should resolve this bug as well as improve Workbench so that we can continue with other tasks while long queries are running.
[1 Jun 2011 17:54] MySQL Verification Team
Thank you for the bug report.
[1 Sep 2011 15:42] Philip Olson
Fixed as of 5.2.35:

+        On Microsoft Windows, expensive queries caused &workbench; to be
+        unresponsive after other applications were made active, and the
+        &workbench; wizard was running. This meant that the main
+        &workbench; window could not be selected.