Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 489 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
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
I'm not sure if this is by design, definitely annoys me. Couldn't find an existing bug, apologies if it's already here.
On a fresh install of Windows 7.
* I maximise the window, or place it to fill the left half of the screen (by dragging it to the left edge of the monitor).
* I double-click or press enter to open another document from the "Solution" pad.
* The window is restored to a different position, no longer maximised or filling the left half of the screen.
Expected: The window not to move when changing which document is open. Note that performing the same document switch through the Window menu or Ctrl-Tab does not move the window.
It's not by design. AFAICT it's caused by GTK not updating the window state correctly when it's maximized or half-maximized using the new Windows 7 commands. It doesn't happen if you maximise "old-style" with the window's maximize button.
I committed a workaround in MD some time ago but the underlying GTK issue remains, so leaving the bug open.