Tell me I'm correct about the following:
It is impossible to use mx:MenuBar with mnemonics and/or have 'Ctrl+Alt+Key' appear in the menu as you can with FlexNativeMenu or NativeMenu.
It is impossible to use any Alt+Key shortcuts to activate a control without Windows® beeping at you when you use the key.
It is impossible to use a s:Button or even an mx:Button with an underlined letter without making a specific skin just for that button.
It is impossible to comprehend why such a standard activation method -- using the Alt+Key would be overlooked by a company leading the pack in RIA or any other type of interface development.
So who is on drugs, I hope it is me and not Adobe.
Wait, don't tell me-- you want me to extend your framework so it includes these fundamental things??
After further research, the way to get around alt-key beeping and get rid of the system menu in a chromeless app is to use:
stage.displayState = StageDisplayState.FULL_SCREEN_INTERACTIVE;
and then do some restructuring so your outer client window is now fully transparent and has no skin, and your inner client window is a child who can be moved or sized in its container.
But, this solution does not allow native window states: Minimized, etc. The best you can do is emulate them, but the OS will only see a window that only has one possible state.
Since it has no system/native menu, the OS won't beep on alt+key. I am speaking of windows only, and have no idea what goes on in a Mac environment with this work-around.