Bug 2501 - Application output pad does not persist its state correctly
Summary: Application output pad does not persist its state correctly
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Docking ()
Version: Trunk
Hardware: PC Mac OS
: High normal
Target Milestone: ---
Assignee: Lluis Sanchez
Depends on:
Reported: 2011-12-14 16:00 UTC by Mikayla Hutchinson [MSFT]
Modified: 2012-01-25 15:26 UTC (History)
1 user (show)

Tags: trident
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 Mikayla Hutchinson [MSFT] 2011-12-14 16:00:46 UTC
If the application output pad is moved to some location other than the default, then MD is quit, then it will not correctly persist that state and restore it when MD is re-opened.

For example, if the pad is moved to the right of MD and docked, i.e. not autohidden. After MD is restarted and an app is run, the pad will be *autohidden*, not docked.

Even stranger, if the pad was docked at the bottom, then after MD is restarted it will be autohidden at the TOP of the window.
Comment 1 Lluis Sanchez 2012-01-25 15:26:09 UTC
Fixed in master.