[any way to kill all delayed calls? [SOLVED]]

Interesting. Had never read anything about that. Thanks for the tip.

[any way to kill all delayed calls? [SOLVED]]

That's sort of what I was after. The API Documentation does not mention this, so I never tried it.

 

How would this work if I called an anonymous (temporarily created) function, like:

 

TweenMax.delayedCall(1, function()

{

trace("test");

});

[any way to kill all delayed calls? [SOLVED]]

What about killAllOf(this), or something similar? I'd like to remove all delayed calls within an object, as opposed to global. The only other way I can think of is to put each into their own variable, or use Timer()

[TweenMax and ContextMenus]

I may create an example file when I get some more free time, but for now I think I'll leave it. I'd just figured that it might be TweenMax since that's the only thing I didn't write

[TweenMax and ContextMenus]

My current FLA is really large and complicated. Yes, I'm running a Mac, and what you mentioned really does sound like the root of my problem. Perhaps you could submit this as a bug to Adobe; they'd probably listen to you faster than they'd listen to me.

[TweenMax and ContextMenus]

For some reason, on more than one occasion, tweens using TweenMax do not seem to work when initiated from a ContextMenuItem listener. If I put it into a delayedCall(0.001), it works! Very strange.

 

I haven't tested TweenLite.

[TweenEvent.COMPLETE conflict with Event.COMPLETE]

Well, I've always used a custom events class for things like this, but this time I figured it'd be better to use the standard ones. But, I just noticed VideoEvent.COMPLETE as well, so... meh, heh... I still think my idea is better, but it would've had to have been applied across the board in AS3

 

Thanks for your thoughts, and thanks for TweenMax!

[TweenEvent.COMPLETE conflict with Event.COMPLETE]

Loader and URLLoader both make use of Event.COMPLETE, however there is TimerEvent.TIMER_COMPLETE, so I think you're right about TWEEN_COMPLETE. What would you think about officially adding such events to the class and deprecating the old ones? Much like what you've done with setDestination() and updateTo()

[TweenEvent.COMPLETE conflict with Event.COMPLETE]

If you aren't going to make this change, lemme know, cuz I'd rather not find out later when I overwrite my files with a new version.

[TweenEvent.COMPLETE conflict with Event.COMPLETE]

I have custom dispatched events in a class:

 

dispatchEvent( new Event(Event.COMPLETE) );

dispatchEvent( new TweenEvent(TweenEvent.COMPLETE) );

 

Since both have a value of "complete", it's causing problems. Adding an event.type check is, to me, unnecessary code. Just to be clear, I'm not saying change the "COMPLETE", but the "complete".

[TweenEvent.COMPLETE conflict with Event.COMPLETE]

Both of them have a text value of "complete". If you have listeners for both events in a single class, you'll have problems.

 

I push for a notion to have TweenEvent.COMPLETE officially changed to "tweenComplete". Would probably be a good idea to change "init" and the others too. I have made these changes in my current project.