> 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. G
