MySQL Bugs: #37175: Some tabs and other controls disappear in Windows XP SP3 when switching MSVDM

Bug #37175	Some tabs and other controls disappear in Windows XP SP3 when switching MSVDM
Submitted:	3 Jun 2008 23:26	Modified:	13 Sep 2008 3:48
Reporter:	Phil Nickerson	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.0.22	OS:	Windows (XP SP3)
Assigned to:		CPU Architecture:	Any
Tags:	MSVDM, objects disappear, XP

Description:
When using the Microsoft Virtual Desktop (MSVDM) when you switch context to another desktop and then return to the desktop in which Workbench resides, several tabs disappear and some controls such as the "MySQL Model" cease to work.  The rest of the Workbench seems to work, but without the tabs, it is necessary to halt Workbench and start it back up.

A work around is to minimize Workbench before switching MSVDM contexts and maximizing it upon return, but this is a pain.

Several other appllications have experienced this over time and the various venders have repaired the problem.  The most recent I have dealt with is WinSCP.  It is a know issue that Windows appliction developers have to deal with.  Not being one, I do not know the magic, only that several apps have fixed this in the last couple of years on XP.

How to repeat:
Start up MSVDM.  Open Workbench and load a project.  Double click on a table in the EER view so the details area appears below.  Note the lower tabs "Table, Columns, Indexes, Foreign Keys, Triggers, etc...".  Keep Wrokbench open in the desktop and switch to another desktop and then return to the desktop with Workbench and notice that this tabs are gone.

Suggested fix:
Seek out other sourceforge projects or other projects like WinSCP to determine their corrective action and follow suite.

NOTE: This behavior was in SP2 as well

Thank you for a problem report. Please, try to repeat with a newer version, 5.0.24, and inform about the results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".