Ultrashock released a new series of Flash MX 2004 tutorials

Ultrashock has just released a whole series of tutorials on Flash MX 2004.

I was asked to write an article on Flash MX 2004 ActionScript 2.0.

Other topics include:

There are a few things I left out of the tutorial because of the little time I had:

Error class
try {} catch() {} throw {} finally {}
New event model
EventDispatcher vs. AsBroadcaster

7 replies on “Ultrashock released a new series of Flash MX 2004 tutorials”

The best is to contact Ultrashock – the copyright holder of the articles. In particular, contact Aral Balkan ( and tell him you’d like a printable version.

BTW, I’ve submitted some changes after the article was written. However, the changes have not been incorporated into the current article. I know they plan on updating the tutorials shortly and will incorporate the changes. Perhaps that would be a good time to create printable versions of the tutorials too.

Thank you Dave. it’s just my lazy a**.
I mean I could just save all pages and do some editing with DWMX – and print it, hehe.
I really enjoy your blog. Keep it up!

Nice article! Summarizes the AS2 news way better than the Flash help pages, (too bad I had already read them).

What I’m realy curious about though, is the stuff you didn’t write about:

Error class
try {} catch() {} throw {} finally {}
New event model
EventDispatcher vs. AsBroadcaster

Is this included in the changes you’ve made or is there any chance you’ll write about this and publish it somewhere else on the web so I can get hold of your superior knowledge.

(Got a bit cringy, but I’m just dying to know)

First, thnx for writing the article. But more importend, thnx for pointing out that ehh (how should i call it) unexpected behaviour of non-primitive objects. U tell there about how and when it occurs in somewhat hard english :). But if u would have written about it i would have been busy for days and days to find the problem.

The problem again:
non-primitive objects wich are defined outside the constructor (class properties) are owned by the class and not by the instance of the class. To be sure the non-primitive objects are owned by seperate instaces, u must define them again in the class constructor.

Maybe it would be nice if u had in your article an example of this, instead of only an example on when it goes wrong.

This behaviour can come in handy though, when u need all instances of a class to share some data (i now use it for depth).

Thnx and greetz Erik

Leave a Reply

Your email address will not be published. Required fields are marked *