I'm seeing very erratic behaviour from the Mac OS default
To keep the best user experience, I have an AIR app start
with a hidden window, which immediately opens another application
window. This is the main user interface. The hidden window creates
the application menus, and adds an entry to the Window menu. Whilst
the main user interface window is open the entry on the Window menu
works perfectly (ie. it triggers events), but once it is closed,
the entry no longer triggers events - in fact no item on the Window
menu does. This entry on the Window menu is intended to open the
main user interface window if closed, or reactivate it if not in
focus - good UI practice I imagine.
If I add the menu entry to the File menu however (not a
default menu in my solution) the events correctly occur, so I guess
the work around is to create my own Window menu, which I'll try - I
wanted to notify Adobe of this issue.
I've ended up rewriting the Window menu and now it works as
expected. As I'm now having trouble with the application menu on OS
X, should I expect that AIR simply does not work with the existing
It's not quite the same issue, but the effects are the same.
Nothing from the eventlistener, or perhaps the eventlistener isn't
set up - is there any way to programmatically check if there is an
eventlistener on an element, in this case a menu?