Search

Can CMDIChildWndEx be made floatable? by Tom-Pham

Active

1
0
Sign in
to vote
Type: Bug
ID: 776366
Opened: 1/11/2013 12:19:37 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
Is there a way to make MDI child windows (CMDIChildWndEx) floatable to the main window (CMDIFrameWndEx) like other CDockablePane(s)? This way the child windows can be dragged out of the main window onto separate monitors, without having to resize the main window across several screens. Basically, child windows tear off like Visual Studio.

Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

NA

Product Language

English

Operating System

Windows 7

Operating System Language

English

Actual results

NA

Expected results

NA
File Attachments
0 attachments
Sign in to post a comment.
Posted by Tom-Pham on 1/15/2013 at 12:47 PM
If anyone thinks this would be a useful feature, you can vote for it here: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3554408-make-mfc-mdi-child-windows-capable-of-tearing-off-
Posted by Microsoft on 1/14/2013 at 4:18 PM
Hello,

Thanks for the report. It is not possible to float an MDI window in an MFC application (as it is in Visual Studio itself). This would be a rather large feature to add in MFC, but we will take it as a suggestion for a future product. You can also submit your request via the "Submit Idea" button on the Connect site for Visual Studio at http://connect.microsoft.com/VisualStudio.

Pat Brenner
Visual C++ Libraries Development
Posted by Microsoft on 1/13/2013 at 10:39 PM
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 Microsoft on 1/11/2013 at 12:51 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)
Sign in to post a workaround.