A Snap Size Dialog Class

While creating a fairly complex resizable dialog application, I became annoyed with the amount the controls flickered while being sized. What I wanted was something along the lines of the rubber band sizing available with Plus!, where the contents of the application are sized only when the dragging action is finished.

The solution I came up with sizes the contents of the dialog only when the dragging action is finished, whether or not "Size window contents while dragging" is checked in the Plus! settings.

  1. Add SnapDlg.h to your StdAfx.h.
  2. Derive your dialog class from CSnapDlg.
  3. Change your dialog's constructor to call CSnapDlg's constructor:
  4. CSnapDialogDlg::CSnapDialogDlg(CWnd* pParent /*=NULL*)
       : CSnapDlg(CSnapDialogDlg::IDD, pParent)
    
  5. Change your dialog's message map to flow through CSnapDlg:
  6. BEGIN_MESSAGE_MAP(CSnapDialogDlg, CSnapDlg)
  7. Overload the virtual function SizeDialog() to size your dialog's contents.
  8. Make sure your dialog's OnSize, OnSizing, OnInitDialog, and OnCaptureChanged handlers call the member functions of CSnapDlg instead of CDialog.

Download demo project - 32 KB

Download source - 2 KB



About the Author

Mike Scanlon

Visit http://mike.pricklysoft.com.

Comments

  • Sizing dialogs

    Posted by Legacy on 05/13/2002 12:00am

    Originally posted by: Davon

    This is exactly what I was looking for. Thanks.

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

Top White Papers and Webcasts

  • Ever-increasing workloads and the challenge of containing costs leave companies conflicted by the need for increased processing capacity while limiting physical expansion. Migration to HP's new generation of increased-density rack-and-blade servers can address growing demands for compute capacity while reducing costly sprawl. Sponsored by: HP and Intel® Xeon® processors Intel, the Intel logo, and Xeon Inside are trademarks of Intel Corporation in the U.S. and/or other countries. HP is the sponsor …

  • 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.

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds