It's not often I run across something I didn't know as simple as this. In fact I'm a little embarrassed that I didn't know this, but it gives me comfort that some other people I talked to also didn't know.What is this of which I speak? Well it may or may not be fairly common knowledge that normally, when you place a bitmap from your library onto the workarea (a.k.a. "the stage" though technically, it's never really the stage, at least not the same stage ActionScript refers to) in the Flash Professional authoring tool, that bitmap becomes a shape, or a part of a shape consisting of other bitmap or vector graphics within the same layer or z-ordering group, once you publish your SWF. A quick test will reveal this behavior:Create a new FlaFile > Import > Import to Stage...Add the following frame script:trace(getChildAt(0));Test movieResult?[object Shape]If you didn't already know that, that's interesting enough. How then, you may ask, do you get an actual Bitmap instance on the stage in Flash? Until yesterday, I thought you couldn't except through ActionScript. But it turns out that is not true. Bitmap objects on the stage will become Bitmap instances rather than shapes if that bitmap image is exported for ActionScript (via library item properties).Edit the image imported in the above example to be exported for ActionScript and run again to get the following:[object Bitmap]In other words, that image on the timeline has become a true bitmap instance rather than part of a shape. The Flash GUI still doesn't give you options for things like instance names or anything at this point, but the object available in the display list is in fact a true Bitmap.

If you're a Flash/Flex developer, you've likely seen those Flash Player error dialogs resulting from unhandled ActionScript errors.These appear when you have the debugger version of Flash Player installed and you run a SWF with errors in the code that are not handled correctly, either through appropriate logic, try..catch blocks, or the correct event listeners. But what if you don't want them?

Have you ever been making a code selection in Flex builder and suddenly the selection resets itself, starting over again from the current position of the mouse?This has been KILLING me. But apparently not many people have seen this? Either that or they don't seem to be vocal about it. Well, now's your chance, there's a bug logged about it (thank you Tim) here:http://bugs.adobe.com/jira/browse/FB-20121.So if you've experienced this, vote for the bug to help get rid of it!

Ok, I didn't necessarily "lie" per se, but I did leave out some vital information in one of my ActionScript 3.0 tips of the day, for..in and for each..in. There I claimed that ActionScript 3.0 "maintains array element order (using numeric array indices) when using for..in and for each..in". But does it?