Distinguishing between 'Print' from 'Print Preview', and 'Print' from a menu or tool bar command.

If your print and print preview works with user defined options it may be required for you to distinguish the print call from a Print Preview screen against that from menu or toolbar. That way you can avoid asking the user for options again in the case of a Print from Print Preview.

Here is a simple solution. When you hit the Print button from a preview screen, MFC generates a message ID - ID_FILE_PRINT which will be mapped to CView OnFilePrint() in your message map when you autogenerate the project. If you go into your resource menu (provided you have an auto generated menu resource) and check the ID of the menu item Print (under File menu) you will see it also has an ID - ID_FILE_PRINT. You need to change this to something else say ID_FILE_PRINTX, then go into Print menu item and change it to ID_FILE_PRINTX too. Overload both messages in your view as

Now you know which is which.


  • Printing problems from the internet

    Posted by Legacy on 01/25/2004 12:00am

    Originally posted by: Nellvella Moffett

    Please help I changed the cartriage for the color and black printer now my computer will not print from the internet.

    Thanj you

  • Feedback

    Posted by Legacy on 08/14/2003 12:00am

    Originally posted by: David Monjo

    Helped me, DM

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • As the mobile enterprise marketplace expands and customer needs grow more diverse, Samsung recognizes that solution partners and developers play an essential role by continually innovating to meet their customers' needs. Samsung works to provide these developers and partners with the latest tools and resources needed to create these solutions. Read this program guide to learn how the Samsung Enterprise Alliance Program provides partners and developers with Samsung enterprise software development kits (SDKs) …

  • Moving from an on-premises environment to Office 365 does not remove the need to plan for disruptions or reduce the business risk requirements for protecting email services. If anything, some risks increase with a move to the cloud. Read how to ease the transition every business faces if considering or already migrating to cloud email. This white paper discusses: Setting expectations when migrating to Office 365 Understanding the implications of relying solely on Exchange Online security Necessary archiving …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date