Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!ucsd!ogccse!blake!uw-beaver!uw-june!roper
From: roper@cs.washington.edu (Michael Roper)
Newsgroups: comp.windows.ms
Subject: Re: cursor keys in dialog controls
Keywords: dialog contol
Message-ID: <9195@june.cs.washington.edu>
Date: 16 Sep 89 04:51:41 GMT
References: <185@sdgsun.COM>
Organization: U of Washington, Computer Science, Seattle
Lines: 16

> 	The problem lies in the keyboard interface.  Apparently the
> dialog box handler is not passing the cursor keys to my control.

That's correct.  The dialog box manager traps those messages
which are part of the standard dialog box keyboard interface.
As you have learned, those include the arrow keys (used to cycle
the input focus among controls in a group) and the tab key (used
to cycle among the groups in a dialog box).  

If you have a control that needs to see these messages, it can
process the WM_GETDLGCODE message sent by the dialog manager.  
The return value indicates which messages the control wants to 
handle.  See the SDK for the details.

Michael Roper
hDC Computer Corp.