Disabling All Top Level Thread Windows

In my current project I found it nessassary to disable all the top level windows my application created before displaying any modal dialog boxes. This is because although all of these windows are "owned" by my main frame window, they are siblings and running a modal dialog does not prevent user input from reaching those windows. I came up with this brutally simple class that disables all the top level windows of a given thread when constructed and re-enables them when it is destroyed. I thought I would share this with you.


class DisableTaskWindows
{
public:
 DisableTaskWindows()
  { ::EnumWindows(EnumWindowsProc, FALSE); }
 ~DisableTaskWindows()
  { ::EnumWindows(EnumWindowsProc, TRUE); }

private:
 static BOOL CALLBACK EnumWindowsProc(HWND hwnd, LPARAM lParam);
};

BOOL CALLBACK DisableTaskWindows::EnumWindowsProc(HWND hwnd, LPARAM lParam)
{
 if (::GetWindowThreadProcessId(hwnd, NULL) == ::GetCurrentThreadId())
  ::EnableWindow(hwnd, lParam);
 return TRUE;
}

It becomes a little more complicated if you need to specify the thread ID:



class DisableTaskWindows
{
public:
 DisableTaskWindows(DWORD dwThreadID);
 ~DisableTaskWindows();

private:
 static BOOL CALLBACK EnumWindowsProc(HWND hwnd, LPARAM lParam);

 BOOL m_bEnable;
 DWORD m_dwThreadID;
};

BOOL CALLBACK DisableTaskWindows::EnumWindowsProc(HWND hwnd, LPARAM lParam)
{
 if (::GetWindowThreadProcessId(hwnd, NULL) == ((DisableTaskWindows*)lParam)->m_dwThreadID)
  ::EnableWindow(hwnd, ((DisableTaskWindows*)lParam)->m_bEnable);
 return TRUE;
}

DisableTaskWindows::DisableTaskWindows(DWORD dwThreadID)
 : m_dwThreadID(dwThreadID)
{
 m_bEnable = FALSE;
 ::EnumWindows(EnumWindowsProc, (LPARAM)this);
}

DisableTaskWindows::~DisableTaskWindows()
{
 m_bEnable = TRUE;
 ::EnumWindows(EnumWindowsProc, (LPARAM)this);
}

It's very simple to use:


CMyDialog dlg;
{
 DisableTaskWindows dtw;
 - or -
 DisableTaskWindows dtw(AfxGetThread()->m_nThreadID);
 dlg.DoModal();
} // Destroys dtw which re-enables the windows

You could also create a class derived from CDialog, override DoModal and add a DisableTaskWindows object before calling the base class. This would make it even more seemless:


class CDisablingDialog : public CDialog
{
public:
 CDisablingDialog(LPCTSTR lpszTemplateName, CWnd* pParentWnd = NULL)
  : CDialog(lpszTemplateName, pParentWnd) {}

 CDisablingDialog(UINT nIDTemplate, CWnd* pParentWnd = NULL)
  : CDialog(nIDTemplate, pParentWnd) {}

 virtual int DoModal()
 {
  DisableTaskWindows dtw;
  return CDialog::DoModal();
 }
};

There are lot's of combinations you could come up with, but I'll leave that as an excercise for the reader.

Date Last Updated: April 24, 1999



Comments

  • Hmm

    Posted by Legacy on 10/18/2001 12:00am

    Originally posted by: Hmm

    Well, I was searching for some etxra info on the procedure DisableTaskWindows from Borland's VCL. You might wnna credit them/it...

    Reply
  • Thanks

    Posted by Legacy on 04/28/1999 12:00am

    Originally posted by: Randy Pitz

    I've been looking for this type of functionality for a long time. Thanks!

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

Top White Papers and Webcasts

  • Wednesday, September 24, 2014 8:00 AM - 9:00 AM PDT According to a recent Forrester Research report, many companies are choosing low-code platforms over traditional programming platforms, due to the speed with which low-code apps can be assembled and tested. With customer-facing applications on the rise, traditional programming platforms simply can't keep up with the "short schedules and rapid change cycles" required to develop these applications. Check out this upcoming webinar and join Clay Richardson from …

  • Live Event Date: September 10, 2014 @ 11:00 a.m. ET / 8:00 a.m. PT Modern mobile applications connect systems-of-engagement (mobile apps) with systems-of-record (traditional IT) to deliver new and innovative business value. But the lifecycle for development of mobile apps is also new and different. Emerging trends in mobile development call for faster delivery of incremental features, coupled with feedback from the users of the app "in the wild". This loop of continuous delivery and continuous feedback is …

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds