tulamide
Far be it of me to question someone with your far greater knowledge and experience with CC, but if 'wait' isn't bugged in any way, then isn't it far more understandable just to put 'wait 2000' rather than what you have done?
I've never had a problem with the wait command, but am willing to concede to you're experience if it is the case.
zen
<img src="smileys/smiley1.gif" border="0" align="middle" />
It was just my personal opinion, nothing universally valid.
I hate the wait object <img src="smileys/smiley17.gif" border="0" align="middle" />
While it is convenient, at the same time it leads to bad maintainable event sheets, whose logic is not easy to find out.
You see, I confirmed it being convenient, but at the cost of easier maintainance.
+ on button clicked
-> create object
-> wait 100 ms
-> set color filter to red
-> wait 2000 ms
-> set color filter to blue
-> wait 2000 ms
-> set x to 40
-> wait 1500 ms
-> set x to 100
-> wait 1000 ms
-> set width to 300
-> wait 50 ms
-> set width to 280
-> wait 50 ms
-> set width to 260
-> wait 50 ms
-> set width to 240
-> wait 50 ms
-> set width to 220
-> wait 50 ms
-> set width to 200
-> wait 4000 ms
-> close application
I find this horrible. But it is valid. The problem is, it indicates that these are actions to be done when a button is clicked, but it isn't. It is a set of actions that cover a sequence of over 12 seconds and is indeed a little program of its own, stuffed into one event.
Now try to make changes. Like setting the color filter to blue only if another sprite is also blue...
But again, this is only my personal opinion. Nothing to worry about. If something fits your needs then use it. Seriously.