On 21 July 2011 03:31, Greg Brown <gk_br...@verizon.net> wrote: >> Display#getActiveDisplay() would be useful, since the (global) >> UnprocessedKeyHandler could use it to "dispatch" to the active Display. But >> that's kind of a workaround for what I was hoping to get. In the referenced >> thread, Chris and/or I suggested that there be another step in the >> pseudocode above -- if there's an active display, but no identifiable >> "destinationComponent" to send it to, then try sending it to the active >> display's key handler before going to UnprocessedKeyHandler. > > Right. That's what I was suggesting as well. The simplest solution is to > modify DisplayHost to send the keystroke to its corresponding Display > instance if no component currently has the focus. > Can you clarify the 'no component currently has the focus' part? Are you saying this would only occur if there is no Pivot Component in the entire app?
I thought the crucial part of this was to dispatch the event to the Display hosted in the OS window considered 'active', even if there is a focused Pivot Component in another Display.
