In general, no, it isn't possible to detect if another arbitrary AIR application is active or not. If you wrote all the apps yourself, you could, conceivably pass messages between your apps using local connection (or, starting in AIR 2.0, using UDP or TCP sockets).
You are right. I've alredy tried with the localconnection and everything works good (launching only one air application from the launcher).
But I've faced with another problem, when I've tried to launch two external air applications from the launcher. I think that in this case I have a problem with the timer event.
What am I doing wrong?
Thanks in advance,
code.zip 973 bytes
I can't really tell what is going wrong.
Here's some information on how the local connection works that might help you figure it out: http://blogs.adobe.com/simplicity/2009/08/using_localconnection_reliably.html
Since each access of the connection locks the shared memory segment, I wonder if you would have better luck only sending a single message per timer event, rather than sending a message per app per timer event. That's just a guess though.