Convert modal dialogs to modeless

Many postings to CodeGuru and similar discussion groups are questions about modeless dialogs and how to keep them from blocking the parent thread. I use a user interface thread to start a conventional modal dialog that behaves modeless-ly and it's so minimalist and easy I thought others may be interested...

Instructions

  1. In your header file define a CWinThread-derived class...
      class CDialogThread : public CWinThread { DECLARE_DYNCREATE(CDialogThread) CDialogThread() {}; virtual BOOL InitInstance(); };
  2. Put this in your implementation file (where CSomeDialog is a conventional dialog class defined the usual way).
      IMPLEMENT_DYNCREATE(CDialogThread, CWinThread) BOOL CDialogThread::InitInstance() { CSomeDialog dlg; dlg.DoModal(); return FALSE; }
  3. To create an instance of your (now-modeless) modal dialog, do this...
      AfxBeginThread ( RUNTIME_CLASS(CDialogThread) );
  4. You can end the dialog the normal way by calling CDialog::EndDialog(), CDialog::OnCancel() or CDialog::OnOK(). All those special caveats about modeless dialogs (like "don't call EndDialog") no longer apply with this approach.

  5. One point to note is the return of 'FALSE' from the InitInstance() override. This tells MFC that the thread didn't start successfully, so MFC does our cleanup for us! Note that by this time the dialog has already returned and we're through with the thread. This is the same thing MFC-generated code does in the InitInstance() of dialog-based applications.


Comments

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

Top White Papers and Webcasts

  • The mobile revolution and the need for mobile apps have created an unprecedented set of challenges for IT organizations. This eBook discuss these challenges and how organizations can address them by making their mobile app development processes more efficient and more effective.

  • Do you spend a lot of time thinking about your enemies? Attacker attribution - figuring out who's out to get you - is one of the most important things an organization can do to protect itself.  Because you have no hope of defending yourself if you don't understand who the attackers are. Good news? Every organization isn't targeted by all the attackers. Bad news? No one can identify your potential attackers as well as you. Read this graphics-rich threat summary for 2014 to determine who might be your next …

Most Popular Programming Stories

More for Developers

RSS Feeds

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