You can define a "modifier" function for almost any property; this modifier intercepts the value that GSAP would normally apply on each update ("tick"), feeds it to your function as the first parameter and lets you run custom logic, returning a new value that GSAP should then apply. This is perfect for tasks like snapping, clamping, wrapping, or other dynamic effects. It's completely up to you!
Parameters: value, target
The modifier functions are passed two parameters:
- value (number | string) - the about-to-be-applied value from the regular tween. This is often a number, but could be a string based on whatever the property requires. For example if you're animating the
xproperty, it would be a number, but if you're animating the
leftproperty it could be something like
"212px", or for the
boxShadowproperty it could be
"10px 5px 10px rgb(255,0,0)".
- target (object) - the target itself
For example, change the x of one object based on the y of another object or change rotation based on the direction it is moving. Below are some examples that will help you get familiarized with the syntax.
The tween below animates 360 degrees but the modifier function forces the value to jump to the closest 45-degree increment. Take note how the modifier function gets passed the value of the property that is being modified, in this case a
Clamp with Modulus
The tween below animates
x to 500 but the modifier function forces the value to wrap so that it's always between 0 and 100.
Have you ever built a carousel and wrestled with making it loop seamlessly? Perhaps you duplicated each asset or wrote some code that moved each item back to the beginning when it reached the end. With ModifiersPlugin you can get a seamless repeating carousel with a single
staggerTo()! The example below tweens each box to a relative x position of
"+=500". Click the "show overflow" button to see each box get reset to x:0 when it goes beyond 500...
We've only scratched the surface of what ModifiersPlugin can do. Our moderator Blake Bowen has been putting this new plugin to the test and has an impressive collection of demos that will surely inspire you.
- ModifiersPlugin requires TweenLite or TweenMax version 1.19.0 or later.
- RoundPropsPlugin taps into the same mechanism internally as ModifiersPlugin (to maximize efficiency, minimize memory, and keep kb down). Think of a
roundPropstween as just a shortcut that creates a modifier that applies
Math.round(), thus you cannot do BOTH roundProps and a modifier on the same property. It's easy to get that functionality, though, by just doing Math.round() inside the modifier function.