The default Key-Traversal, or Tab navigation, code is hard to
over-ride.

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:

    Window.setNavigationPolicy(NavigationPolicy nav)

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     )



======================================================================

Consume KeyEvent in one of the KeyListener's.
======================================================================

See also 4077817.
  xxxxx@xxxxx   1998-02-03

Currently planning to implement this functionality, or equivalent
functionality, in the merlin focus enhancements.
  xxxxx@xxxxx   1999-12-14

Consuming the key-event is only possible when the key-event is received.
If it's a listener to a JFrame, the key-event for the tab-key is never received,
 whereas for the Frame
the key-pressed event is received, but the key-released event is not received.
We need the key-pressed as well as the key-released event.