Search the Community
Showing results for tags 'TweenMax TweenLite'.
Found 1 result
-
OK, I've wondered about this for the longest time and have decided to ask for your opinions... I find myself building a lot of user interface stuff (menus, etc) and I'm always at odds of how to handle this. For a super basic example, consider this: Suppose I have five menu items and I want to have the the active one at full opacity and the other four at half opacity. So when a menu item is clicked, it goes to full opacity and the one that was at full opacity fades to half opacity. Simple, right? In jQuery, I can assign an "activeButton" class to the one that has been clicked and then use that as the selector to fade it when another is clicked... and then of course un-assign that class to the old button and assign it to the new active button. OR (and here is where I think this may be cheating) I can tell ALL of the other buttons to fade, even though only one of them really needs to fade and be on my way! I've done it both ways and never noticed any difference or performance hit from tweening all of them... but I'm not sure if there are other ramifications. I used to do the same thing in AS at times, but honestly with jQuery, using not() makes it too easy: $('.menuButtons').not('#thisButton') Thoughts? If something is being asked to tween to X even though its already at X, does it take up much in the way of resources? So should I be losing sleep over this? I find myself "cheating" when I'm in a time crunch, but maybe there's no problem with it?
