Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!hp-pcd!hpcvlx!gabe
From: gabe@hpcvlx.cv.hp.com (Gabe Begeddov)
Newsgroups: comp.windows.x.motif
Subject: Re: Setting keyboard focus
Message-ID: <110630036@hpcvlx.cv.hp.com>
Date: 13 Mar 91 01:39:40 GMT
References: <1991Mar7.124545@MAX7.llnl.gov>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 13

XmProcessTraversal tries to disallow traversal to what it considers
a non-traversable destination.  Lots of resource settings play a
part in this decision such as XmNtraversalOn, XmNnavigationType.  In 
addition, it requires that the destination and all it's ancestors
(up to the shell) be at least partially unobscured and managed.
This means that you can't call XmProcessTraversal till after the 
hierarchy is realized.  It would have been nice to have had a 
pre-realize mode to setting the focus so that the initial focus
could be set at startup.  I think 1.2 is addressing this problem 
of initial focus specification. Till then you have to wait till 
realize to set the traversal.

Gabe