Greg, I don't want to presume to speak for Bill (hopefully he will be able to comment soon), but I thought this was about having a desktop app with multiple Displays in multiple 'native OS windows'.
To paraphrase from the original thread - A desktop app might create a new Display (and therefore java.awt.Dialog/org.apache.pivot.wtk.DesktopApplicationContext.HostDialog) via org.apache.pivot.wtk.DesktopApplicationContext.createDisplay(int, int, int, int, boolean, boolean, boolean, Window, DisplayListener) That Display might have a ComponentKeyListener whose purpose is to close the DesktopApplicationContext.HostDialog when Escape is pressed. If that Display doesn't contain a focused Component, the ComponentKeyListener will never be called, and there is no other obvious place to listen for such a keyboard event. http://apache-pivot-users.399431.n3.nabble.com/KeyListeners-on-ImageView-tp2600622p2636565.html http://apache-pivot-users.399431.n3.nabble.com/KeyListeners-on-ImageView-tp2600622p2653507.html http://apache-pivot-users.399431.n3.nabble.com/KeyListeners-on-ImageView-tp2600622p2654940.html > Windows behaves that way, but Mac OS X does not. On the Mac (as in Pivot), > the concepts of "active" and "focused" are independent So based on your reply in the last of the 3 links above, this ticket could perhaps be summarised along the lines of 'Add support for MS Windows style behaviour when dispatching keyboard events to active OS windows, in addition to the Max OS X style behaviour that is currently supported.' Bill - Please clarify if and when you see this thread. On 21 July 2011 02:42, Greg Brown <gk_br...@verizon.net> wrote: >> A new method, Display#getActiveDisplay(), would return the Display >> considered to be active in the eyes of the current OS/application. > > The "active" display is defined by the active native window. It is > independent of the active Pivot window. > > Only Pivot frames show an active state (and then, only when they are not > maximized). That implies that this would be an issue only when using > multiple, non-maximized frames spanning multiple Pivot displays. That seems > like a pretty unusual use case. > > G > >
