Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!zazen!uwvax!ub.d.umn.edu!cs.umn.edu!uc!shamash!hare.udev.cdc.com!slc1290
From: slc1290@hare.udev.cdc.com (steve chesney x4662)
Newsgroups: comp.windows.x.motif
Subject: Keyboard Focus
Message-ID: <30328@shamash.cdc.com>
Date: 4 Feb 91 15:36:51 GMT
Sender: usenet@shamash.cdc.com
Reply-To: slc1290@hare.udev.cdc.com (steve chesney x4662)
Organization: Control Data
Lines: 21

We are using Motif 1.1 and have noticed that when we create a dialog box
(usually a dialog shell, bulletin board, list widget and push button combo),
keyboard focus is not realized until the pointer leaves the window and 
moves back into it.  We are setting keyboard focus to a list widget or a scroll
bar using process traversal.

This is particularly unfortunate due to the fact that the default button does 
not work till the keyboard focus is realized.  Thus the user has to move the
pointer out of the window, then back in to use the default button!  This 
situation occurs even if the window materializes directly beneath the pointer;
it still has to be moved out, then in again to use the keyboar for default 
button, scrolling or selection from a list widget.

This situation does not occur if there are any text or text field widgets in
the dialog box; keyboard focus is seen immediately if the pointer is in the
window.

Is this standard Motif behavior, and can I get around it?
-- 

Steve Chesney       Control Data Corporation      slc1290@hare.udev.cdc.com