It looks like you're new here. If you want to get involved, click one of these buttons!
function movieClips() mcA = movieClip.new{ {1,10, thisSprite} } mcB = movieClip.new{ {1,10, thatSprite, {tweening properties}} } function levelA() control movieClip mcA here end function levelB() control movieClip mcB here end end |
Comments
movieClip.new()
instead of
MovieClip.new()
?
(this should actually throw an error except if you have a movieClip already defined, in which case it could do strange things like the one you explain in your post).
Fragmenter - animated loop machine and IKONOMIKON - the memory game
No errors, just tweens that doesn't behave as defined (as far as I can see some scale tweens that got lost and some tweens that happened at other frames than defined). All movieclips are named differently.
The tweens were correct if mcB were played first, and also when repeated.
Not correct if played after mcA, also not correct when mcB is repeated after that.
Fragmenter - animated loop machine and IKONOMIKON - the memory game
I can recreate the "problem" by moving line 3 (function playnoCard()) to about line 34 (after the third movieclip guideAnim_Dra), leaving the movieclips outside the function that controls them, then the tweens doesn't behave as expected when played AFTER the last movieclip animEyes_Hej.
I guess one could try to recreate this with a simplier from-the-scratch example code, but I haven't got the time to do that (yet).
You may have other comments about my code (optimization etc), but please focus on the problem at hand. B-)
Likes: saeys
at least you could make it work properly, even though you never got the cause of the problem.
Likes: saeys
Fragmenter - animated loop machine and IKONOMIKON - the memory game