Print-preview behavior in VC4.2b.
Pradeep Tapadiya -- pradeep@nuview.com Monday, December 16, 1996 Environment: VC++ 4.2b, NT 4.0 Netters, For an MFC based MDI application, with VC++ versions prior to 4.2b, print-preview window used to appear in a maximized mode and take over the whole main frame window. This behavior seems to have been changed in 4.2b. Now print-preview takes over the active MDI view and does not appear in a maximized state. As a consequence, if the active view has been minimized and the user clicks on print-preview, he would never know that the print-preview window is actually up. Is this a bug or has the behavior been changed for a good reason? Thank you. Pradeep
Dave Kolb -- sasdxk@wnt.sas.com Thursday, January 09, 1997 I tried this with my app, old and new versions, and this is indeed true. In my case, most of my toolbar icons are immediately greyed when I hit print preview, so I guess I get some indication. The views stay minimized as you say. I guess I like this behavior better though as the benefit is that I can run print preview on multiple views at the same time which I like. Try it. Dave Kolb -----Original Message----- From: Pradeep Tapadiya [SMTP:pradeep@nuview.com] Sent: Monday, December 16, 1996 6:33 PM To: mfc-l@netcom.com Subject: Print-preview behavior in VC4.2b. Environment: VC++ 4.2b, NT 4.0 Netters, For an MFC based MDI application, with VC++ versions prior to 4.2b, print-preview window used to appear in a maximized mode and take over the whole main frame window. This behavior seems to have been changed in 4.2b. Now print-preview takes over the active MDI view and does not appear in a maximized state. As a consequence, if the active view has been minimized and the user clicks on print-preview, he would never know that the print-preview window is actually up. Is this a bug or has the behavior been changed for a good reason? Thank you. Pradeep
Mike Blaszczak -- mikeblas@nwlink.com Saturday, January 11, 1997 >From: Pradeep Tapadiya [SMTP:pradeep@nuview.com] >Sent: Monday, December 16, 1996 6:33 PM >Now print-preview takes over the active MDI view >and does not appear in a maximized state. As a consequence, if the >active view has been minimized and the user clicks on print-preview, >he would never know that the print-preview window is actually up. The code was originally changed for the 4.2b release because an active DocObject server couldn't get a reliable frame window while trying to perform print preview. You'll find that the next release of MFC will use the main frame window as a parent for the preview view if the child frame is minimized or not available, and use the child frame otherwise. .B ekiM http://www.nwlink.com/~mikeblas/ Why does the "new" Corvette look like a 1993 RX-7? These words are my own. I do not speak on behalf of Microsoft.
Murray Davidson -- murray@yc.estec.esa.nl Monday, January 13, 1997 The new behaviour has some advantages -- see several previews in different views simultaneously. But it gave us a rather amusing screenful with our MDI app that had non-resizable, dialog-based views! Fortunately, the extreme left-hand edge of the Close button of the preview toolbar was *just* visible so that we could close it. [Although I could have started up another app to find out what the accelarator was.] I was a bit disappointed that there was no way to revert to the original pre-4.2b functionality, e.g. by specifying the frame in which to place the preview, as an option. [The views are now resizable, although that isn't quite what we had originally designed for.] //Murray -- Murray Davidson. European Space Agency, Post Box 299, 2200 AG Noordwijk, NL murray@yc.estec.esa.nl Tel. +31 71 565-4025 Fax +31 71 565-6142
| Вернуться в корень Архива |