Name: mc57594 Date: 02/07/97
The default Key-Traversal, or Tab navigation, code is hard to
We need to be able to do our own Keyboard navigation and not
have the default Key navigation occur, currently this must be
done by having one of the KeyListeners "consume" the KeyEvent.
There should be a method call like:
That can be used to customize the Navigation policy (for more
than just Tab and Shift Tab also) or set it to a null value
to indicate that none is required.
In other words, externalise the Navigation logic, and allow us
to write our own, and set it in place.
( This would also help with the fact that the current Nav )
( policy is rather broken at the moment - it's rather )
( random and not consistent across Windows NT/Solaris )
company - Oracle Corporation , email - ###@###.###