Bug 6822 - Application chooses wrong monitor
Summary: Application chooses wrong monitor
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Shell ()
Version: 3.0.x
Hardware: PC Windows
: Low normal
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
Depends on:
Reported: 2012-09-01 04:33 UTC by Alex Conway
Modified: 2017-07-28 14:44 UTC (History)
4 users (show)

Tags: gtk
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 6822 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:

Description Alex Conway 2012-09-01 04:33:01 UTC
I have two monitors attached to my computer (windows XP, all up to date):
number 1 is a TV on the HDMI adn the desktop is extended on to this
number 2 is monitor on DVI and is the Primary
after I installed MonoDevelop and run it for the first time, it chose number 1, instead of the primary, forcing me to search for my remote control to turn the TV over to HDIM so I could move the monodevelop window over to the primary monitor.

Then when I 'Restored Down', the window suddenly stretched across both monitors!

finally, after maximising it to the primary monitor and closing, when I re-started it appeared maximised on monitor number1.
Comment 1 iain 2016-04-20 16:24:33 UTC

*** This bug has been marked as a duplicate of bug 6691 ***
Comment 2 Alex Conway 2017-06-01 19:10:47 UTC
This is not a duplicate of bug 6691. Only the second part is.
Maybe 13 years ago I should have posted two separate bugs.
The bug is:
I have two monitors attached to my computer (windows XP, all up to date)
number 1 is a Full-HD TV on the HDMI
number 2 is monitor on DVI
The Primary monitor is number 2 and the desktop is extended across both monitors.
After I installed MonoDevelop and run it for the first time, it started up on monitor number 1 instead of the Primary monitor.
(At the time the TV did not have the HDMI input selected)

The Primary monitor is not necessarily monitor 1

I have not used Monodevelop since I posted this bug.
Comment 3 Mike Krüger 2017-06-07 08:26:51 UTC
I can't confirm that bug because I don't have a dual monitor setup but I think it's an issue that affects all OSes.

But I don't think that there is a way to force a window that we start with a process to be created on a special monitor. Does visual studio do the right thing ?
Comment 4 Jordan Matthiesen [MSFT] 2017-07-28 14:44:22 UTC
Confirmed this is still happening with MonoDevelop on Windows.