This content has been marked as final. Show 3 replies
yeah this is typical when using a timeline based button action. two things you could do:
1) control the state change by using a variable to indicate when the motion is complete (or not) like 'isOpen' - you'd need to do this for each button in combination with a condition in the handler that 'reads' the var and determines the course of action - of course the next problem is that if you 'rollout' while the motion is happening and the handler fires previous to the setting of the var to it's 'new' state it won't close because the condition would only be fired once - the only way around that would be to include a loop that runs until the condition is satisfied.
2) much better than the above method (which would get messy fast) is to simply use the 'tween' class to create you motions, you can then 'open' or 'close' from what ever the current position of the clip is at the moment the handler is fired. you've got your code on the timeline of the 'button' MC (good job) so you could change it to something like this:
Thanks so much! The second option fixed it right up, Just a little bit of tweaking with the variables and its done. looks sleeker too!
Thanks for the quick solution!
you're welcome - no problem :)