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


ON_COMMAND(ID_FILE_PRINT, OnFilePrint)
ON_COMMAND(ID_FILE_PRINTX, OnFilePrintFromMenuOrToolBar)
Now you know which is which.



Comments

  • 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

    Reply
  • Feedback

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

    Originally posted by: David Monjo

    Helped me, DM

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

Top White Papers and Webcasts

  • The mobile market is white hot. Building a well-crafted product development plan that addresses market research, strategy, design, and development will provide the greatest chance for success. Each phase of an app's lifecycle is critical to the its overall success and feeds into the next step of the process of product development for the app. This white paper examines the five key phases of mobile app creation, one by one, to understand how they work together to help create a successful mobile app.

  • Today's agile organizations pose operations teams with a tremendous challenge: to deploy new releases to production immediately after development and testing is completed. To ensure that applications are deployed successfully, an automatic and transparent process is required. We refer to this process as Zero Touch Deployment™. This white paper reviews two approaches to Zero Touch Deployment--a script-based solution and a release automation platform. The article discusses how each can solve the key …

Most Popular Programming Stories

More for Developers

RSS Feeds

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