Jump to content

Mike D

  • Posts

  • Joined

  • Last visited

About Mike D

Mike D's Achievements

  1. One other note, I'm using TimelineLite in my app, and I also used TimelineLite in my codpen - where things are working fine.
  2. Hi all, I'm running GSAP v1.19.x and according to the docs x/yPercent has been supported since 1.13.x. What's strange is I created a codepen with version 1.19.x and it works just fine. The ask here I guess is - what, if anything, in the way of css styles or tween attributes could override or somehow prevent x/yPercent from outputting percentages? Thanks and sorry kind of a random question here.
  3. Thanks Jack. I cleared cached, deleted the `node_modules` folder and reinstalled and am still having the same issue. I'm wondering if the culprit is a collection of custom npm packages that are running gsap 1.19 as a peer dependency. Hmmm...
  4. Hi, I'm getting this error when trying to bundle in webpack. I have read through many posts on these forums pertaining to npm usage and feel I'm up to speed on correct usage. What's interesting is webpack-dev-server is working fine but the issue only crops up with uglify when bundling. Line 4822 = const {Ease, Linear, Power0, Power1, Power2, Power3, Power4, TweenPlugin} = _gsScope; I'm running webpack 2.2.1 and gsap 2.0.1. Any help is greatly appreciated. - MD
  5. Thanks a lot Carl, I JUST figured it out before rechecking this post.
  6. Hi guys, Does anyone know how to creat the equivalent of this TWEEN function using Greensock? new TWEEN.Tween({ val: 0 }) .to({ val: 1 }, 500) .easing(TWEEN.Easing.Circular.InOut) .onUpdate(function () { // some logic here }) .onComplete(function () { // some logic here }).start(); Thank you.
  7. Hi guys, So I have a "default" class for an element that places it offscreen and ready to be animated in. I remove the "default" class in the tween which works just fine. <style> .myelement { left: 0px; } .myelement.default { left: -200px } </style> TweenLite.to(".myelement",speed, { className: "-=default" }); Now, I have some scaling logic in place that is fired on resize. When resized, the "left" property is updated which now needs to overwrite the ".myelement" left value contained in the element's .myelement class. TweenLite.to(".myelement",speed, { className: "-=default", left: "-300px" }); My guess is that the ".myelement" left value is overwriting the passed "left" parameter. Any suggestions on optimizing this is greatly appreciated. - Mike D
  8. Oh, i didn't realize there was already a plugin for this. Thanks guys!
  9. Hi Jack and crew, Thank you for all the work that has gone into the best animation library on the planet. It's a pleasure to use and the support is stellar. I'm not sure if there is any sort of "suggestion box"... if so, I'd love to put Cubic Bezier support at the top of the list. This would be such a killer feature. Thanks!
  10. Thanks Jonathan! Greatly appreciate the pointers!
  11. The yoyo option looks great, I'm wondering if this was the fix? http://jsfiddle.net/droplab/FCbUz/4/
  12. Good call on the yoyo, wasn't aware of that option. However, I'd like to have the tween fire and then return to x:0,y:0,z:0 The overall concept is these *wedges* are shooting out from the middle and then returning to the center, each time with a random radius/length. Thanks!
  13. Here's a fiddle displaying the issue I'm having. I need to figure out how to have the overlapping tweens transition smoothly without jumping. http://jsfiddle.net/droplab/FCbUz/3/
  14. Thanks for the reply. I actually don't as this piece is buried deeply within the app logic. I can try and create a reduced test case to better illustrate the issue.
  15. Hi, I'm trying to use GSAP to animate objects in a ThreeJS project, within the requestAnimationFrame loop. Obviously this loop is firing much faster than the time it takes each tween to complete. I'm getting lots of overlapping Tweens on each object and I'm trying to figure out the best way to have each Tween run and then run it's onComplete function to tween itself back properly without losing it's references. Would TimelineLite be better suited for this or is there a better approach using TweenLite? Thanks in advance! function animate() { if(animation === true ) requestAnimationFrame( animate ); TweenLite.killTweensOf(object); TweenLite.to(object, 0.5, { x: _radius * Math.cos( num ), y: _radius * Math.sin( num ), ease: Expo.easeOut, onComplete: function(_this,_x,_y) { // animate the object properties back to what they were before we started this tween }, onCompleteParams: ["{self}",object.position.x,object.position.y] }); }