[comp.windows.x.motif] Keyboard traversal and the XmMainWindow widget

steve@mnetor.UUCP (Steve Rees) (03/23/91)

Howdy,

I'm having significant trouble getting keyboard traversal to work within a
mainWindow.  Here's my setup: a mainWindow, which contains an XmForm 
widget in the client area, which in turn contains a rowCol, 3 buttons, and
another widget.  I want to be able to traverse the rowCol and 3 buttons,
so I do XmAddTabGroup() on all 4.  No problem.   I can tab/arrow around 
to my heart's content.  The problem is that whenever I select something
from one of the pulldown menues in the mainWindow's menubar, focus is not
returned to where it came from.  Example: suppose focus is on button1.  I
open up the edit menu (using either mouse or keyboard) and select something.
When the menu closes, focus doesn't return to button1, but goes to button2
instead!  It always goes to the group after the one that had focus before the
menu was posted.  I've seen this problem before, in other situations, and I've
always been able to get around it by suitable choices of tab groups (cycling
through tab groups seems to be a symptom of confusion on Motif's part about
where focus should be after some event.)  I've tried making different 
combinations of the mainWindow, menubar, cascade buttons and pulldown 
menues tab groups as well, but to no avail.  Does anybody have a solution?

Thanks in advance,
Steve
-- 
    Steve Rees
{uunet|utzoo}!mnetor!steve or (better) steve%mnetor.uucp@uunet.uu.net
Ma Bell: +1 416 475 8980  ext. 322
					Why isn't ping pong called pik pok?