lab@sdgsun.COM (Larry Baird) (09/15/89)
I am attempting to create a window control similar to the list box control. My control will use a call back function to get new text as it is scrolled into view. The benefit of this control will be that not all of the data will need to fit into memory. This will allow this control to browse such items as files and data bases. The problem lies in the keyboard interface. Apparently the dialog box handler is not passing the cursor keys to my control. I recieve all other keys except ALT keys, tab and shift-tab without any problem. The list box control uses cursor keys to scroll through its list, so I know it can be done. Does anybody have any ideas on how I can make my control receive those ornery old cursor keys? thanks, lab -- Larry A. Baird Software Design Group, Inc. Manager, Software Development 450 N. Lakemont Avenue UUCP:ucf-cs!sdgsun!lab Winter Park, FL 32792 CIS: 72355,171 (407) 657-1300
roper@cs.washington.edu (Michael Roper) (09/16/89)
> 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.