> That was supposed to say '...if there is no *focused* Pivot Component...'
> I don't foresee too many arguments regarding which Component to
> dispatch keyboard events to when the Pivot app has no Components!

Ah, that makes more sense.  :-)

> I have seen occasions where one OS window (MS Windows XP 64) would be
> highlighted/active/focused, but there was a focused Pivot Component in
> a different Display.
> ...
> Digging a little deeper suggests that
> org.apache.pivot.wtk.ApplicationContext.DisplayHost.processFocusEvent(FocusEvent)
> is designed to ensure that this scenario will not arise by clearing
> and setting the focused Pivot Component on
> java.awt.event.FocusEvent.FOCUS_LOST and
> java.awt.event.FocusEvent.FOCUS_GAINED

Right.

> Given the existing mechanism to ensure that the focused Pivot
> Component will always be in the active OS window, forwarding the key
> stroke to the Display would suffice for this ticket.
> 
> Any problems with focused Component remaining in a non active OS
> window would a separate issue.

Makes sense to me.

G

Reply via email to