Bug 7776 - Updater focus behavior makes killing monodevelop impossible if loading a solution fails
Summary: Updater focus behavior makes killing monodevelop impossible if loading a solu...
Status: RESOLVED DUPLICATE of bug 4919
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Updater ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-10-10 13:26 UTC by Jackson Harper
Modified: 2012-10-10 13:47 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED DUPLICATE of bug 4919

Description Jackson Harper 2012-10-10 13:26:58 UTC
Probably best explained with this video:

http://screencast.com/t/9x2u7sJ44

I'm not sure why the solution if failing to load (will likely file a separate issue for that) however, the updater constant focus stealing behavior makes killing monodevelop or just moving it out of the way to wait for the solution to load impossible.
Comment 1 Jackson Harper 2012-10-10 13:47:43 UTC
I guess this is actually a duplicate of https://bugzilla.xamarin.com/show_bug.cgi?id=4919

*** This bug has been marked as a duplicate of bug 4919 ***