Flash Camp Atlanta (Aug 28th) - Registration Is Open

Just got word that Flash Camp Atlanta registration is now open. It will be held August 28th 2009 at the World Congress Center. Early bird prices are only $41 through July 30th - get your tickets now! Details for those too lazy to click the link:

"Flash Camp Atlanta is a full-day event focusing on the Adobe Flash Platform. Enhance your skills in ActionScript and Flex while learning from local and national industry experts. Flash Camp will provide an introduction to the Flash Platform as well as covering advanced topics for existing Flex and ActionScript developers. In addition to great training, there will also be many giveaways as well as a chance to network with other developers in the community. In addition to a great Main Session (9am-5pm) there will also be a special Introductory Session (8-9am) for developers who are new to the Adobe Flash Platform. This special session only costs an additional $15 (until July 30th and $25 thereafter). This session will get these developers up to speed aspects of the Flash Platform like Adobe Flex, AIR, and Flash Builder."

Comments (0)

How to Debug Fullscreen AIR Apps on a Secondary Display

Like many developers, I have a dual monitor setup. I also have certain monitors that over time have become the "Home Display" for certain programs. I almost always write code on the left-hand display (my OS primary). Firefox and applications I am developing are virtually always on the right-hand display.

So I've been developing a full screen AIR app lately and have been irritated that the AIR application always wants to open on my primary display, thus covering my IDE and also covering any debug controls in Flex Builder. For awhile I moved Flex Builder over to the right-hand screen, but that just felt wrong, so today I figured out how to programmatically move the AIR app to the secondary display.

Turns out it just took one line of code (line 10 below), setting the stage's x coordinates to the righthand boundary of my primary display (which is also the left-boundary of my right-hand display). Now this might be old hat for Flash developers, but not for me. I thought I'd post a little mini-app example of making this work.

Note that your milage with this example may vary if you:

  1. Only have one display (it will move the AIR app out of your visible area)
  2. Your displays are setup to be above each other rather than beside each other (same result as 1)
  3. Your primary OS display is on the right (same again)

If you are looking to do something different with multiple displays, check out the Livedocs page for Enumerating the screens and the ASDoc for the Screen class.

UPDATE (10:20am)

Okay, so I thought better of my solution. This code does the same thing, but just moves the AIR app to the rightmost display. If there is only one display it will just stay there.

Comments (2)

Flex 3 Final - Run Air App and Nothing Happens

I just ran into a somewhat frustrating to debug problem with running the final release of Flex builder. I just upgraded to the final release version of Flex Builder 3 from a beta version, and I found that suddenly my AIR projects would no longer run from the IDE. When I clicked the "Run As Adobe AIR Application" button - nothing happened. No error, no nothing, it just doesn't seem to do a thing. Then I tried running the running the app in debug mode and got this error:

Process terminated without establishing connection to debugger.

Command:

"C:\Program Files\Adobe\Flex Builder 3 Plug-in\sdks\3.0.0\bin\adl.exe"
C:\wwwroot\MyApp\bin-debug\MyApp-app.xml 
C:\wwwroot\MyApp\bin-debug 

Output from command:

invalid application descriptor: descriptor version does not match runtime version

After a little Googling around and hitting a few dead ends, I finally found the simple solution on this post on Brian Rinaldi's Blog. For any AIR apps you created in earlier versions of Flex builder, you're going to want to take a look sat the application's xml descriptor and make sure it matches the version of the AIR runtime you are developing for. Just open up the descriptor XML file and make sure that the namespace specified is "http://ns.adobe.com/air/application/1.0", not "http://ns.adobe.com/air/application/1.0.M6", which was the last beta version.

Comments (3)