Hi, Transform manager is working fine when the Static MovieClip. If I am created dynamic movice and apply Transform Manager, I am phase.
![]()
3.2.5- IMPROVED: if you accidentally pass a number in to ScrambleTextPlugin as the new text, it'll cast it as a string.- IMPROVED: if you set extendTimeline: true on a gsap.registerEffect, the timeline instance will be passed as the 3rd parameter to the effect.- IMPROVED: EaselPlugin will do its best to automatically set the cache on the target element according to its nominalBounds.- FIXED: setting the duration of a Timeline didn't alter the timeScale properly (but it did if you set totalDuration). See- FIXED: worked around a Firefox browser bug that interrupted pointermove events on Draggable items when using touch.
See- FIXED: setting the delay via the delay method after creating the animation didn't actually move its startTime.- FIXED: setting an animation's startTime directly via the startTime method wouldn't always work if the parent timeline had sorting disabled. It also wouldn't re-active the tween if altering the startTime was done after it completed.- FIXED: (regression) if you set reversed: true on an animation, it would start from the end rather than just keeping the playhead at the start.- FIXED: if you call update on a Draggable insance WHILE it is being dragged and autoScroll is true, and the element is nested inside a container that's not scrollable, it wouldn't update the position correctly. 3.2.4- FIXED: Regression in 3.2.0 caused onReverseComplete to fire when resuming a paused animation from its very beginning which also caused the.then Promise to be resolved (prematurely). The onReverseComplete could also be triggered incorrectly when the parent timeline's playhead moves backward to before the child tween starts but it's only supposed to fire when the actual animation itself is reversed (regardless of the parent's orientation). See- FIXED: Draggable didn't set its rotationOrigin initially upon creation (required a press).
![]()
Mar 2, 2020. 3.2.3- FIXED: a regression in 3.2.2 could cause immediateRender not to get triggered properly in some rare cases.- FIXED: if you set a defaults object on a timeline with immediateRender, it was getting overridden by the function's default value.- IMPROVED: if you don't provide a point to MotionPathPlugin.convertCoordinates, it'll return a Matrix2D object that you can reuse to convert individual points more cheaply.- IMPROVED: MotionPathPlugin.getRelativePosition accepts point objects (or Arrays) now for the fromOrigin and toOrigin parameters, making it more flexible. Same for MotionPathPlugin.getAlignMatrix.
Mar 2, 2020. 3.2.1- NEW: Added MotionPathPlugin.convertCoordinates method.- IMPROVED: adjusted some plumbing to make it easier to create an unofficial ClassNamePlugin;)- FIXED: the 'align' feature of MotionPathPlugin wasn't working correctly when the target was a root element due to browser quirks related to SVG size reporting. A workaround is in place now.
See- FIXED: if you try to apply a transform-related property to an SVG element that's not in the DOM yet, Firefox would throw an error. See- FIXED: if you clone an SVG element with transforms and then apply transforms to that clone, they wouldn't line up properly because the origin data wasn't recorded in a data attribute. See- FIXED: if you set a 'start' or 'end' on a motion path that lands exactly on top of an anchor point that's directly next in line from the other start/end of the slice, it wouldn't slice it properly. See- FIXED: if you add a callback to the very start of a timeline that had already completed, and it has autoRemoveChildren:true, it may not fire.
See- FIXED: if you tried setting/tweening a transform-related value to NaN or undefined, it would allow it in 3.2.0 (regression). See- FIXED: if you defined a callback with parameters (like onCompleteParams) INSIDE an advanced stagger object, it wasn't recognized. See- FIXED: an error that'd prevent timeline.tweenTo from working properly (regression).
See- FIXED: Draggable elements with position: 'fixed' that are NOT type: 'rotation' wouldn't be positioned correctly after scrolling the page. See- FIXED: if an SVG element had transforms applied OUTSIDE of GSAP, they could be parsed incorrectly. See.
Feb 27, 2020. 3.2.0- NEW: MotionPathPlugin recognizes a new 'alignOrigin' value that controls the point on the target that gets aligned with the path. Previously it was always the top left corner (of the bounding box). Setting an alignOrigin also automatically sets the transformOrigin to the corresponding place on the target for convenience. AlignOrigin is an Array with progress values along the x and y axis, so 0.5, 0.5 would be in the center, 1, 0 would be the top right corner, etc. If you don't want to have the transformOrigin set to match automatically, pass false as the 3rd array element, like 0.5, 0.5, false.- NEW: MotionPathPlugin.getRelativePosition method that calculates the x/y distance between two elements based on the coordinate space of the 'fromElement', even if both elements are nested inside different containers that have various transforms applied!
This makes it simple to move one element to another one no matter how deeply nested they are.- NEW: MotionPathPlugin.getAlignMatrix method that generates a matrix object (with a, b, c, d, e, and f properties just like an SVGMatrix) for aligning two elements and converting between their coordinate spaces.- NEW: PixiPlugin can do directional rotation now. For example, if you animate to rotation: '-270short' it will go in the shortest direction. '-270cw' would always go in the clockwise direction, and '-270ccw' would go counter-clockwise.- IMPROVED: added one more digit of precision to decimals to accommodate edge cases where that's perceptible.
See- IMPROVED: frame rate isn't capped at 60fps anymore (though the browser is in charge of deciding how often it'll dispatch requestAnimationFrame).- IMPROVED: sometimes the browser reports a complex CSS value with the color in a different place than what the user provides. For example, the user may try animating a filter to 'drop-shadow(0px 0px 10px #f00)' whereas the browser reports the current value as 'drop-shadow(rgb(0, 0, 255) 0px 0px 10px)', so the start/end values don't map properly. The algorithm has been improved to sense that condition and move the color in the starting value accordingly.- IMPROVED: worked around several bugs in Safari that cause motionPath animations to fail.
![]()
See- IMPROVED: fixed/added various TypeScript definitions- FIXED: timeline.tweenTo didn't recognize 'duration' or 'ease' if they were provided in the vars object. See- FIXED: if an object was returned from the onFulfilled callback of animation.then that wasn't a Promise or a function, it could generate an error. See- FIXED: in very rare cases, a zero-second animation/callback may not perform its final render.
See- FIXED: in Draggable, if you startDrag and pass in an mouse event (instead of a pointer event) even though the browser supports pointer events, the onDragEnd may not be triggered properly. See- FIXED: zero-duration animations may not resolve a Promise. See- FIXED: if you tried animating a element with MotionPathPlugin with an 'align' specified, it may not align properly. See- FIXED: in a VERY rare scenario a tween may do its final render as if it's ALMOST at the end (but not quite) when the duration is a very long decimal.- FIXED: if there are no active tweens for a while (and thus GSAP goes to 'sleep'), unpausing a tween could lead to it triggering a callback at the incorrect time on that very first tick (as if the resuming animation's startTime wasn't adjusted yet).
See- FIXED: when using the 'back.in' ease, autoAlpha may not set the final visibility value properly. 3.1.1- FIXED: the 'all.js' ES module file contained an invalid export for TweenMax (regression in 3.1.0). See- FIXED: if a zero-duration timeline contained a callback that added more animations to itself (lengthening the timeline's duration), it may prematurely get removed from its parent timeline.- FIXED: if an object is returned when resolving then that's not a function or Promise, it could generate an error.- FIXED: transformPerspective now renders first in the list of transforms (previously it was AFTER translate/translate3d). This makes things render the way it did in GSAP 2 and earlier.
See. Jan 24, 2020.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |