which are typically primitive widgets that act as tab group members. Furthermore, manager widgets must handle all of
the input events for gadgets, so there is a great deal of functionality that supports keyboard traversal written into the
Manager widget class.
Before we discuss the details of dealing with tab groups, there are a few things we should mention. The
implementation of tab groups has changed from earlier versions of the toolkit; to maintain backwards compatibility,
remnants of the older implementation are still resident in the current implementation, which may cause some
confusion in the current API. The technology of keyboard traversal is still being improved. Although later
implementations may not change the existing API, new versions of the toolkit may optimize the process substantially.
Since the current implementation of tab groups is not perfect, some people want to change the default behavior and
control it entirely on their own. We do not recommend this approach. You should avoid interfering with the keyboard
traversal mechanisms, as it will make it easier to maintain compatibility with other Motif applications and it won't
require any changes for new versions of the toolkit. If you are going to modify the operation of keyboard traversal,
you should be careful and test your changes thoroughly.
9.8.1 Turning Traversal Off
You can prevent a widget from participating in keyboard traversal by removing the widget from the traversal list. To
remove a widget from the traversal ...