Bug 5466 - Active layout is switched to Visual Design even if the source code editor is still displayed
Summary: Active layout is switched to Visual Design even if the source code editor is ...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Docking ()
Version: 3.0.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-06-02 12:05 UTC by pinggi
Modified: 2017-08-08 14:46 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 pinggi 2012-06-02 12:05:44 UTC
I develop GTK# app and don't use visual designer at all.
One file MainWindow.cs contains a class:

public partial class MainWindow: Gtk.Window
// ...

When I switch from 'Main.cs' tab to 'MainWindow.cs' tab, the active layout is switched from 'Solution' to 'Visual Design'. It causes the opening of the Toolbox, etc. and I need to switch back. It is very annoying.

What I suggest is switching to 'Visual Design' only if the bottom tab of the 'MainWindow.cs' tab is switched to 'Designer' instead of the 'Source'.
Comment 1 Jordan Matthiesen [MSFT] 2017-08-08 14:46:26 UTC
Thanks for reporting this issue, testing with recent builds I'm seeing that this issue is now fixed.