Print Preview Enhancements

New users of this class will have to visit Robin's article for the relevant download material and then update the .cpp/.h files with the versions provided in this article. Old users of the class can just replace their existing .cpp/.h files with these.

Overview of New Functionality

This is an update of the nice class provided in Robin's article and includes the following features:
  • The print preview will now never show empty preview pages unless the user views 2 pages of output when only 1 is available.
  • Print preview will now respond to WM_MOUSEWHEEL messages appropriately. In "zoom out" mode, it will scroll you through the pages of output. In "zoom in" mode, it will scroll the output page up/down.

Implementation Details

For the mouse wheel to work correctly, you will have to override your CMainFrame::PreTranslateMessage() function as follows:
BOOL CMainFrame::PreTranslateMessage(MSG* pMsg) 
{
 // TODO: Add your specialized code here and/or call the base class
 if (pMsg->message == WM_MOUSEWHEEL)
 {
  CView *pView = GetActiveView() ;
  if (pView != NULL)
   pView->SendMessage(WM_MOUSEWHEEL, pMsg->wParam, pMsg->lParam) ;
 }

 // call the base class here
}
This is required because in print preview mode, the WM_MOUSEWHEEL messages go to the CDialogBar in the window and not directly to the view. This was the only way I could find of easily getting these messages to the CMyPreviewView window.

Downloads

Download source - 6 Kb


About the Author

Roger Allen

Its me!

Comments

  • Article no longer updated

    Posted by Legacy on 12/06/2002 12:00am

    Originally posted by: Roger Allen

    If your interested in this or any other printing article, I maintain my printing articles over on codeproject.

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

Top White Papers and Webcasts

  • With JRebel, developers get to see their code changes immediately, fine-tune their code with incremental changes, debug, explore and deploy their code with ease (both locally and remotely), and ultimately spend more time coding instead of waiting for the dreaded application redeploy to finish. Every time a developer tests a code change it takes minutes to build and deploy the application. JRebel keeps the app server running at all times, so testing is instantaneous and interactive.

  • The exponential growth of data, along with virtualization, is bringing a disruptive level of complexity to your IT infrastructure. Having multiple point solutions for data protection is not the answer, as it adds to the chaos and impedes on your ability to deliver consistent SLAs. Read this white paper to learn how a more holistic view of the infrastructure can help you to unify the data protection schemas by properly evaluating your business needs in order to gain a thorough understanding of the applications …

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds