Re: Keyboard Interface with not DIALOG class Dialog Boxes

Article View: comp.windows.ms

Article #13326

#13326

From: Bill Turner
Date: Mon, 28 Nov 1988 19:10

13 lines
768 bytes

I think the function IsDialogMessage is what handles the keyboard interface
for dialog boxes -- when you have a modeless dialog (created by CreateDialog)
your main message loop needs to be something like

while(GetMessage(...))
{
    if (IsDialogMessage(...))
	continue;
    TranslateMessage(...);
    DispatchMessage(...);
}

--Bill Turner

Technical Details

Message-ID: <106580004@hpcvlx.HP.COM>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!watmath!clyde!att!rutgers!apple!voder!pyramid!hplabs!hp-pcd!hpcvlx!bturner

References: <2282@PEDEV.Columbia.NCR.COM>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!watmath!clyde!att!rutgers!apple!voder!pyramid!hplabs!hp-pcd!hpcvlx!bturner
From: bturner@hpcvlx.HP.COM (Bill Turner)
Newsgroups: comp.windows.ms
Subject: Re: Keyboard Interface with not DIALOG class Dialog Boxes
Message-ID: <106580004@hpcvlx.HP.COM>
Date: 28 Nov 88 19:10:04 GMT
References: <2282@PEDEV.Columbia.NCR.COM>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 13

Reply to Parent Message