In your AIR application, if you overwrite the application menu, you might find that the keyboard shortcuts (e.g. Cmd-C, V) doesn’t work under Mac. It seems the “Edit” menu in the default application is essential to these functions. So you should at least keep the “Edit” menu if you need to use your own menu.
First, your asdoc.exe should be in your system path
asdoc -source-path .\src -doc-sources .Adobe AIR 2 beta is out last night (Nov 16, 2009). It includes a number of highly expected features including launching native applications. It also improves CPU/memory usages. Some sample applications include:
http://labs.adobe.com/technologies/air2/samples/
File Tile
If your AIR application needs to do something (e.g. saving some settings) before quitting, you may listen to the Event.EXITING event, and then preventDefault(), then do something, and finally call NativeApplication.nativeApplication.exit() to quit. But, if you call NativeApplication.nativeApplication.exit() too quickly (e.g. call it right after preventDefault())), your application won’t exit. The solution is to wait some time (e.g. 100 ms) and call this function.
<?xml version="1.0" encoding="utf-8"?>
<mx:WindowedApplication xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" applicationComplete="init();">
<mx:Script>
<![CDATA[
private function init():void
{
NativeApplication.nativeApplication.addEventListener(Event.EXITING, onExiting);
}
private function onExiting(e:Event):void
{
e.preventDefault();
var t:Timer = new Timer(100);
t.addEventListener(TimerEvent.TIMER, onTimer);
t.start();
}
private function onTimer(e:TimerEvent):void
{
NativeApplication.nativeApplication.exit();
}
]]>
</mx:Script>
</mx:WindowedApplication>
If you use mx:WindowedApplication, you won’t have this problem. If you use mx:Application, you may find your application is not visible after launching.
Solution: open your application description file (xxxx-app.xml) and change visible property to true.
How to get a cert in the first place:
http://www.adobe.com/devnet/air/articles/signing_air_applications_print.html
If you encounter this error when signing your AIR application, do the following:
It should be good.
Reference:
http://forums.adobe.com/thread/433530
You can get all applications from Adobe Marketplace
Beautiful Design
Useful functions
When you use mxmlc to compile files, you might encounter this error. You need to add source-path option:
mxmlc -source-path C:/p/y/src/ -file-specs MyClass.as -debug=true
You set systemChrome=”none” but it still doesn’t work? You probably forget to set
showFlexChrome="false"
