In this tutorial we're going to review a set of classes I've just created and published. There are several demo's we will cover in this tutorial to show exactly what these classes can do for your portfolio! Also we'll be reviewing the matrix class and bitmapData class and taking a click look at just one of the ways we can use these two classes together!

Dynamically creating multiple enemies to 'shoot' with the 'gun' you created in my last tutorial.

I noticed an interesting consequence of having an incorrectly defined allowNetworking HTML parameter for one of my Flash projects: Full screen stopped working in IE.The problem was that I gave the allowNetworking parameter a value of "always". Sadly, this is not an allowed value. For some reason, because it was not recognized, on Internet Explorer it meant full screen also broke.The lesson here is that you need to watch your allow* parameters (i.e. allowFullScreen, allowNetworking, and allowScriptAccess). Each have their own set of allowed values which are unrelated to the other.allowFullScreen: [true | false]allowNetworking: [all | internal | none]allowScriptAccess: [always | sameDomain | never]My problem was mistaking allowNetworking values with those of allowScriptAccess. Silly me.

If you haven't noticed, Flash CS4 Professional now supports the use of an External Library Path to reference class definitions in SWC files to be used, but not compiled, in your resulting SWF. What this means is that you can make "child" SWFs that are intended to be loaded into another "parent" SWF and have all, or most, of the class definitions limited to the parent SWF. This reduces the redundancy of those classes in each of the children saving you on bandwidth. Right now, however, Flash has a small problem when using such classes with library symbols.