Bug 13157 - No way to get Document pad back if you undock/close it
Summary: No way to get Document pad back if you undock/close it
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Docking ()
Version: 4.0.9
Hardware: PC Windows
: --- normal
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2013-07-10 15:33 UTC by Jeffrey Stedfast
Modified: 2013-07-11 14:24 UTC (History)
3 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 Jeffrey Stedfast 2013-07-10 15:33:42 UTC
From a customer:

I then managed to lose the document window entirely. It's possible to 'undock' it from the main window, then close it. After that, there's no way to get it back except deleting EditingLayout.xml and effectively resetting to defaults.
Comment 1 Ashley 2013-07-10 19:54:06 UTC
Steps to reproduce:

1) Drag another tool window into the document well, so that a tabbed tool window is formed with 'Documents' and whichever other window you chose.

2) You can now drag the 'Documents' tab out and have it as a floating window.

3) You can now close the window.

4) There is no way to get it back.
Comment 2 Lluis Sanchez 2013-07-11 14:24:01 UTC
A fix will be included in upcoming releases.