Volume 6A: Motif Programming Manual

}

There are some applications that might actually have to be used without a mouse, just as there are some users who

prefer to use the keyboard, so you should be careful about turning off keyboard traversal for the Sashes in a

PanedWindow widget. If you do turn off Sash traversal, we recommend that you document the behavior and provide a

way for the user to control this behavior. For example, you could provide an application−specific resource that

controls whether or not Sashes can be traversed using the keyboard.

As noted earlier, XmNtraversalOn can be set on tab groups (which tend to be manager widgets) as well as tab

group members. If traversal is off for a tab group, none of its members can be traversed. If keyboard traversal is

something that you need to modify in your application, you should probably hard−code XmNtraversalOn values

directly into individual widgets as you create them. Turning off traversal is typically not something that is done on a

per−widget−class basis. When you turn traversal off in application code, be careful to make sure that there is no

reason that a user would want to traverse to the particular widgets because once you hard−code the resource values,

they cannot be modified by the user in a resource file.

9.8.2 Modifying Tab Groups

The XmNnavigationType resource controls whether a widget is a tab group itself or is a member of a tab group.

When this resource is set to XmNONE, the widget is not a tab group, so it defaults to being a member of one. As a

member, ...