AsWing AIR full support version

January 23rd, 2008

Before, we think there will be only on Stage instance for one actionscript programme, but AIR NativeWindow make us know we are wrong. So, for AIR full support, we must remove the dependence on sington Stage instance(for example widely AsWingManager.getStage() calls)。

These days, we got this almost done, now, for a AsWing programme, you can have more than one Stage exists, components here and there on different Stage at same time runs well.

Check this branches

Just little api changed, importances are FocusManager, CursorManager, when you use them, you’ll see, most need you pass Stage param to get the instance, the managers will create/get right instance for you automatically. KeyboardManager now will not be sington too, it’s instances will belongs to JRootPanes.

Hope it can help your AIR developing, feedback/bug reports are helpful. We’ll release a official version when it get stable later.

3 Responses to “AsWing AIR full support version”

  1. kidddon 01 Feb 2008 at 6:26 pm


  2. Michael Plankon 02 Feb 2008 at 5:17 am

    I’ve got a big problem with AsWing_multiStage in combination with AIR b3 (same Problem also with normal AsWingA3 version):

    I have put a drag and drop intensive application inside a JPanel (no AsWing drag and drop). When I start dragging Sprites around, I get the following error window: Visual Studio Just-In Time Debugger… An unhandled exception occured in adl.exe [3692]

    – I have no problems when deploying it in a standard SWF File and open it with Flash Player
    – I have no problems when I only deploy my drag and drop application without AsWing Stuff as AIR application

    … so the combination must be the problem :-(

    Any tips??

  3. iileyon 07 Feb 2008 at 1:16 am

    Hi Michael, it maybe a bug, can you send us a mail with a simple test case project to let us do a test.