button1.dispatchEvent(new MouseEvent(MouseEvent.CLICK));

That triggers the function manually, and should be equivalent to clicking it; the button should be disabled and the first text output will show up.

Also, using “as” will return null if the cast fails. The Datatype() cast will throw an error if the cast fails. There is a performance difference here. If you’re using a Flash Player that throws errors, like the Flash IDE or the debug version of the plugin, the “as” is faster. But in “normal” versions, the Datatype() version is faster. So…it really comes down to preference. I just like the “as” syntax more than the parenthetical syntax, and assurance that I’m avoiding those few instances where the parentheses “get ya.” In areas where optimization is crucial, however, you should use the parentheses.

For anyone else reading this, go check out Davi-T’s work. He’s a motion god!

I’m sorry you feel it’s too complex, but some people are wired one way and other people are wired other ways. I can try to design, but that’s really better left to other people.

I may be wrong (it’s been a while) but I think my original introduction stated that more clearly, and it got edited down a bit. Either way, I apologize for that not being more clear.

I agree, though, that being able to subscribe to comments would be nice. I ended up missing out on quite a few comments since this tutorial first “aired.”

I agree with Erick on his first point: You make some mighty leaps starting in step 9. I understand your logic in avoiding OOP and such for the time being, but since the tutorial to that point was so easy to follow I got real lost real quick. A simple disclaimer would have helped me immensely and saved me some time rereading to see if I had missed something.