1 person found this helpful
I can't tell whether it's AIR desktop or AIR mobile that you're trying to do. Things have progressed a bit in the time since CS3 and 5.5, you can now easily add a later version of AIR to Flash Pro.
In the CS 5.5 days you had to fool Flash Pro into using a later version. You could try the steps shown here:
only when it's talking about using AIR 3.2, we're up to AIR 19 now. I don't know if the overlaying will work, but it's worth trying.
Hopefully some of the difficulties you're seeing have been improved in the 8 1/2 years since CS3 was released.
tnx! unfortunately this does not help in my case, which is to test in my development environment, for air. But I'll check out your blog, which may give me some pointers for some other stuff. Guess I am just pissed at adobe right now: some things look different in air than flash; some time ago the transform functions were implemented wrong (but they were corrected in a patch later), in fireworks, to move a bitmap with shift-arrow, the up arrow would not work.. when I loaded a bitmap, with only one layer and the layer was locked, instead of creating another layer it would start painting and screwing up the locked layer.. and so on and so on.. but these are not free products, those are paid products, that they sell full of bugs
update: the weirdest thing. the problem is that a certain file, when I hit ctrl enter, it will open the flash player, but not the air player if the settings are to test as air
so far, a backup file was running fine (i.e, it runs in the air player with no problem), but if I save the backup as the original, overwriting it, it will run no more in air. Now I tested it backwards; I saved the non running file with some other name, and now it runs fine again. With the precedents, as in deleting the original, and saving the backup with the name of the original, and that new save would not run, it all suggests that the problem is related with the file name. It may not be the file itself, but maybe the registry of the air player itself (I did not know it had a registry, but all this suggests this is the case; also the publish options have an option for the air id of the application, which is probably kept in a registry) is corrupted, or the entry for that file name is corrupted somehow