Dipscom... that nails my misunderstanding, once again. I googled the staggerTo() method, checked out some threads on here, but didn't look at the docs! I guess that is because whenever I've referenced docs in other libraries, they were always hard to comprehend. These docs aren't too bad tho. From here on I'll google it, search the threads, then check docs, before posting. In retrospect it makes sense that there would be a separate parameter for the time between staggers and the position on the timeline at which the tween occurs. Otherwise we would be replacing a necessary parameter/losing functionality when using staggerTo() instead of manually staggering it
Nuggets learned: >time btwn staggers is different then position on timeline >I kind of thought that.. you generally target one object per tween, and if you're targetting multiple, then you generally use a stagger. But those are two different use cases. You can target as many things as you want in one to() or from() tween as long as you put them in an array in the tween >should have known to put all repeating stuff in a var... >being able to set a defaultEase for all tweens is awesome / similar to using putting all eases in a var but even cleaner (surprised it doesn't work with TweenMax) >that way of creating labels via add() is nice. I think of it as labelling a frame in flash. >I think I've read that setting position by label instead of seconds is easier to read, which i guess is true, going to be utilizing labels on future anims Its still a bit weird to me why we don't need to stagger the sets(), and that it doesnt throw off the timing flow of the other staggered tweens. So I checked out the docs there. I like that it clarifies that set() is the exact same thing as any to() or from() tween, with zero as a duration. But set()'s still need to occur on a precise position on the timeline. Actually wait. if they are an instant occurance (no duration) then maybe there is nothing to stagger. its like flick the switch, uses zero duration, onto the next tween