Bug 3776 - MonoDevelop does not start on primary monitor
Summary: MonoDevelop does not start on primary monitor
Status: NEW
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Shell ()
Version: 2.8.6
Hardware: PC Windows
: Low normal
Target Milestone: master
Assignee: Cody Russell
URL:
Depends on:
Blocks:
 
Reported: 2012-03-06 20:41 UTC by wildcoil
Modified: 2016-06-30 15:22 UTC (History)
3 users (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 for Bug 3776 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description wildcoil 2012-03-06 20:41:13 UTC
Summary says it all. Regardless of the last position MonoDevelop was closed in, it always starts maximized on the secondary monitor.

I've searched around, and I found this guy who has the same problem from two years ago:
http://stackoverflow.com/questions/1816486/monodevelop-and-screen-orientation

The problem doesn't seem to have changed since then. I imagine all that's needed is a simple check to ensure the window spawns on the primary monitor. It's very annoying to open it and have to drag it to the primary monitor each time, but it's not critical.

OS: Windows 7 x64
Comment 1 Marius Ungureanu 2013-11-23 20:34:18 UTC
This is a GTK issue, unrelated to MonoDevelop.