Bug 12883 - Xamarin Studio window disappears and reappears when updater is minimized and maximized
Summary: Xamarin Studio window disappears and reappears when updater is minimized and ...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0.9
Hardware: PC Mac OS
: Low trivial
Target Milestone: master
Assignee: Cody Russell
Depends on:
Reported: 2013-06-25 17:38 UTC by PJ
Modified: 2014-12-13 11:24 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description PJ 2013-06-25 17:38:00 UTC
Steps to reproduce:

1. Open the check for updates dialog
2. Minimize the check for updates dialog
3. Maximize the check for updates dialog *by clicking on the Xamarin Studio icon*

Expected behavior:

Updater should maximize with no XS flicker

Actual behavior:

Xamarin Studio disappears and reappears - see http://screencast.com/t/JhOmrelmEou

Filed against:
XS version 4.0.9 (build 12)
Mac OSX.

I was going to check other environments today but I imagine it will be the same and there's too much else going on. It's a trivial issue.
Comment 1 Mikayla Hutchinson [MSFT] 2013-06-25 18:50:43 UTC
I suspect it's because of this workaround:
Comment 2 Marius Ungureanu 2014-12-13 11:24:52 UTC
The hack is no longer there. I can't reproduce it so I guess it's fixed.