Search

Problem with Print Preview in a VS2010SP1 MFC tabbed MDI application with splitter window main frame style by cpp-hacker

Closed
as Fixed Help for as Fixed

1
0
Sign in
to vote
Type: Bug
ID: 717004
Opened: 1/6/2012 1:30:17 AM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
0
User(s) can reproduce this bug
With the wizard of VS2010SP1 I created a MFC tabbed MDI application with DocumentView architeture support and MFC standard project style and Split window main frame style.
If you call "Print Preview" after moving the splitter and closing "Print Preview" the view gets corrupted and is drawn incorrectly.
I posted this problem to the forum
http://social.msdn.microsoft.com/Forums/da-DK/vcmfcatl/thread/1fc696a1-c9bd-4bf9-9e46-5e811799cb27
and Rob Pan [MSFT] MSDN Community Support could reproduce the problem and recommended me to post it to this portal.
Please tell me if there is a workaround/fix/patch available, because I have the problem in a real productive application.
Details (expand)

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

Visual Studio 2010 SP1

Steps to reproduce

0) create the application with VS2010SP1 wizard and enable Split window main frame style.
1) start the application
2) move the splitter to the middle / or somewhere else of the application
3) call print preview from the menu
4) close the preview with the close button

Product Language

English

Operating System

Windows 7

Operating System Language

German

Actual results

The view is now corrupted and drawn incorrectly - you see a scrollbar on the lower right.

Expected results

The view should look the same as before calling "Print Preview".
File Attachments
0 attachments
Sign in to post a comment.
Posted by cpp-hacker on 1/25/2012 at 2:12 AM
Is there a workaround patch/fix available for this problem? I need a solution for this.
Posted by MS-Moderator09 [Feedback Moderator] on 1/8/2012 at 7:32 PM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.
Posted by MS-Moderator01 on 1/6/2012 at 1:44 AM
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.