DarioCru

It worked well Thanks Zach

Thanks for the quick answer Zac Your approach looks clean and makes sense, I was hoping to save some line of code using the function reverse(); I'm going to use many effects and interactions, some of them uses a lot of CPU and I'm trying to do my best for optimising the code and making it light and smooth. In this sense, what do you recommend for small interactions? CSS or JS? which of the two overloads the CPU the most? Tomorrow I will give a try using .tweenFromTo() rather than .reverse(), that will help on saving some line of code, I'm only concern about the behaviour when a tween get interrupted from another interaction (e.g. click and quickly move out while is animating). will it complete the tween and then perform the next one or they will overlap? anyway, in the worst scenario I will create one tween for each status. PS: That's how the universe works if things go well maybe one day you will work with another company called Cru! ?

Hi there, I'm having troubles on managing the status of a button using two timelines. onmouseenter: behaves as expected onclick: it is still ok onmouseleave: on the dark background it is ok, but on the light background (after click), it seems that one of the timelines is not reverting all the elements to their initial status. in particular, I can still see the vertical line and the right-side copy (switch to light UI) that are supposed to be reverted on their initial status (opacity:0). I suspect that is could be related to the fact that the two timelines share some element and that could create conflicts. Also, when the user click quickly on the button while any animation is still running, or move the mouse out immediately after click, it all start behaving in an unexpected way. It must be related to suppressing elements. If you can recommend any solution or best practice it would be very appreciated Thanks