It is possible to dock a CDockablePane to one that has already been closed

It is possible to dock a CDockablePane to one that has already been closed by TOnofre

Closed

as Fixed

Type:	Bug
ID:	585837
Opened:	8/12/2010 10:08:31 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

If you have a floating pane and dock another pane to it so they are either side by side or top to bottom. When you close the left(or top) pane the remaining pane resizes correctly which is great. But if you take another pane and drag it over this floating pane, it is possible to dock it to a "ghost" of where the previous left(top) pane was. Using the Smart docking mode, you get the rectangles for docking that you would expect if that pane was never closed, while also having the options to dock to the entire window like it should behave.

Details (expand)

Visual Studio 2010

Start with a freshly built application (or you can use the VisualStudioDemo sample as I have reproduced it here).
Float one of the CDockablePanes (Say, Class view).
Float a second pane (we'll go with Properties this time), and dock it to class view (doesn't matter whether its top, bottom, left or right, just not tabbed together)
Now close (using the individual pane's X) the pane that is located on the Left OR Top depending on how you docked them.
Float a third pane (let's go with File View).
Drag File view over the floating pane in different spots to see where you can dock it. You should notice smart docking rects that appear to align with the previously closed pane's rect.

English

Windows Vista

English

Current implementation allows for a pane to be docked to a pane that is already closed. If the pane trying to be docked is aligned to be tabbed with the ghoat of this closed pane - the docking pane will disappear.

Docking should not be allowed to positions where the pane is no longer visible.

File Name	Submitted By	Submitted On	File Size
shot5-hoverOverLeftSide.jpg	TOnofre	8/16/2010	37 KB
shot1-dockinglayout.jpg	TOnofre	8/16/2010	43 KB
shot2-closeLeftPaneBefore.jpg	TOnofre	8/16/2010	46 KB
shot3-closeLeftPaneAfter.jpg	TOnofre	8/16/2010	33 KB
shot4-floatPanetoDock.jpg	TOnofre	8/16/2010	36 KB

Posted by Microsoft on 9/22/2010 at 1:20 PM

Hello Tracy,

Thanks for the report and the detailed steps to reproduce. This issue has been fixed in MFC for a future release of Visual Studio.

Pat Brenner
Visual C++ Libraries Development

Posted by TOnofre on 9/20/2010 at 8:30 AM

I was just looking for an update on this issue. Can we expect this to be something that will be fixed in a future release?
Thank you.

Posted by Microsoft on 8/17/2010 at 1:05 AM

Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by TOnofre on 8/16/2010 at 8:00 AM

I have tried to attach a few screen shots depicting the steps taken to reproduce this issue. I will try to also explain specifically to the screen shots as to what steps to take.
1. Starting with the Visual Studio Demo - Open in VS 2010 and run.
2. Click ok on the popup to allow any default settings.
3. Float the Properties and Class View windows and dock them so that the Class View is to the LEFT of Properties (as shown in "shot1-dockinglayout.jpg".
4. Use the X on the Class View pane to close the class view - "shot2-closeLeftPaneBefore.jpg" shows the X being clicked and "shot3-closeLeftPaneAfter.jpg" shows the Properties pane taking up the entire window.
5. Float the Watch pane - "shot4-floatPanetoDock.jpg".
6. Drag the Watch pane and hover over the left side of the Properties pane - you will see the smart docking highlight show up for the area where the ClassView pane USED to be docked - in this screen shot it would dock the watch view to the right of the class view window that is currently not visible - "shot5-hoverOverLeftSide.jpg".

NOTE: if you close the RIGHT side instead of the LEFT side pane - this issue does not occur.

Posted by Microsoft on 8/12/2010 at 10:06 PM

Thanks for reporting this issue. In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

Please give us a video file of this issue so that we can conduct further research.

It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 7 days, we will close this issue.

Thanks again for your efforts and we look forward to hearing from you.

Microsoft Visual Studio Connect Support Team

Posted by Microsoft on 8/12/2010 at 6:06 PM

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)