punchDoes TurboActivate work for versions of Adobe AIR before Adobe AIR 2.0? The Adobe AIR example requires Adobe AIR 2 NativeProcess API, which was first support in AIR 2.
My application is written with Adobe AIR 1.5 and I'm searching for a licensing tool to protect it. I was excited about TurboActivate until I noticed this.
TurboActivate requires Adobe AIR 2.0 and above. This is due to limitations in Adobe AIR 1.x, namely the fact that there was no NativeProcess support for Adobe AIR 1.x.
Is there any reason you can't compile your app for Adobe AIR 2.0? The Flex SDKs are free, so you don't need to purchase anything extra.
punchThanks for the quick reply.
Yeah, I was afraid of that.Our company was using Flash CS3 when the project began and Adobe AIR 2.0 doesn't work with CS3 (it requires Flash CS4 and above). We have since began using CS5.5 on other projects, so I guess now is as good a time as any to begin investigating whether it is possible to update our AIR Application to AIR 2.0 and how to go about doing it.
Any suggestions are appreciated. Meanwhile, Google ho!
Right now we just have the Flash Builder example project. We'll be releasing a Adobe Flash Professional CS5.5 example project with TurboActivate 3.0 (coming very soon). If you need any help adding TurboActivate to your app we'll be glad to give you a hand.
punchYes, I am going through this page:http://wyday.com/limelm/help/using-turboactivate-with-adobe-air/These examples seem associated with a development environment other than Flash CSX.
I managed to update our application to Adobe AIR 2.6. Now it's back to TurboActivate.
Unfortunately, I've already managed to hit a snag. Even though I have both Desktop and Extended Desktop set in the AIR publisher settings, TurboActivate.as is throwing the following error:"You must add <supportedProfiles>extendedDesktop</supportedProfiles> to your Adobe AIR Application Descriptor File (e.g. AppName-app.xml) before you can use TurboActivate."
I look into the descriptor xml file, and I see the following has been generated for the support profiles:<supportedProfiles>desktop extendedDesktop </supportedProfiles>
I look into the TurboActivate.as file and see that the constructor has an if-statement with the following condition:if (NativeProcess.isSupported)which must be failing.
I will continue to tinker with it, but any suggestions in the meantime?
Chris
punchI found what seems to be the source of the problem. In the descriptor xml, I swapped the profiles. So this:<supportedProfiles>desktop extendedDesktop </supportedProfiles>was changed (manually, via text editor) to this:<supportedProfiles>extendedDesktop desktop</supportedProfiles>I also only have extendedDesktop checked in the AIR Publisher Settings.Just thought I'd throw that solution out there in case someone else comes across this thread.
