It doesn't appear to be a MouseEvent.
Yes, but that doesn't mean I'm paying attention. (Or aware of every new feature.)
Here's what I found:
Step 2: Release notes at the bottom: http://labsdownload.adobe.com/pub/labs/flashplatformruntimes/shared/ai r3-3_flashplayer11-3_p3_releasenotes.pdf
Does that help?
That doesn't help but it is good info .
I have the links you posted. That's why I was able to upgrade to AIR 3.3 BETA. My question is can someone at Adobe verify that MouseEvent.RELEASE_OUTSIDE is within the BETA release like it says in the release notes.
Also, what is the correct "official" way to upgrade Flash Builder 4.6 to AIR 3.3.? I performed an rsync command on the directory ( OSX command line ) but was told to do a "ditto" on the beta directory to a copy of the FB SDK 4.6.0 SDK used by Flash Builder.
MouseEvent.RELEASE_OUTSIDE is within AIR 3.3 BETA 3 build after verifying it on windows and mac. The document for this featuere is here http://help.adobe.com/en_US/FlashPlatform/beta/reference/actionscript/ 3/flash/events/MouseEvent.html#RELEASE_OUTSIDE. The feature is enabled from SWF 16, so the -swf-version=16 parameter is needed.
ditto command is all right to upgrate 4.6 to AIR 3.3.
I just double and triple checked my settings. There is no MouseEvent.RELEASE_OUTSIDE within my airglobal.swc. I have followed all of the steps above and can't seem to find it anywhere. I would assume RELEASE_OUTSIDE would come up as an option on anything having MouseEvents like the Spark Button. Is this a premium feature that we may have to pay for?
FB 4.6 ( build 326955)
MouseEvent.RELEASE_OUTSIDE should be available in the Flash Player and AIR beta players. You may need to write your own code to catch it, I wouldn't expect older components to automatically work.
That doesn't make any sense. If you guys (Adobe) update the API (AIR 3.3 BETA) you have to bake any updates into the controls. If you make MouseEvent.RELEASE_OUTSIDE available to me how do you expect me to use it? Where is the sample code using it?
This is a beta release. Code may change, documentation may not be finished, there's a list of known bugs.
The link from simplezeroec contains some example code at the bottom. While it doesn't contain RELEASE_OUTSIDE, it should be trivial to do that.