Jump to content

Search In
  • More options...
Find results that contain...
Find results in...

GreenSock last won the day on November 4

GreenSock had the most liked content!


  • Content Count

  • Joined

  • Last visited

  • Days Won


GreenSock last won the day on November 4

GreenSock had the most liked content!

Community Reputation

8,678 Superhero

About GreenSock

  • Rank

Contact Methods

Profile Information

  • Gender
  • Location
    Chicago Area
  • Interests
    Volleyball, Basketball, Christian Apologetics, Motorcycling

Recent Profile Visitors

49,107 profile views
  1. I'm so sorry - the email notification for this thread wound up in my junk mail filter and I'm just seeing it now. Yes, I'd consider this a bug - it should be fixed in the next release which you can preview at https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/gsap-latest-beta.min.js Thanks for reporting it. Sorry about the confusion that caused.
  2. I'm so sorry - for some reason the email notification for this topic landed in my junk mail filter. Yes, this is fixed in the next release which you can preview at https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/gsap-latest-beta.min.js. I apologize for the regression.
  3. Sorry about that - yes, this edge case was handled differently in v3 on purpose but upon reflection, I think it's best to revert back to the old behavior. That'll happen in the next release which you can preview at: https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/gsap-latest-beta.min.js Thanks for reporting this!
  4. @ZachSaucier the reason it was working for you is because you had an invalid CSS value for display - you had quotes in your CSS declaration around "none" So it wasn't actually display:none to start at all. The "display" behavior was indeed purposeful, as most people animate to display:none to make something vanish at the end, so it's a special case. When GSAP encounters a "display" animation, it applies the value at the end but I could add some code to only do that for display: "none". Obviously if you want to change something like that at the start of the tween, the best way to do it is either with a set() or by doing a fromTo() tween so that you can set initial values too.
  5. This should be resolved in the next release which you can preview at https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/gsap-latest-beta.min.js Thanks for pointing it out.
  6. GreenSock

    gsap3 crash

    Good catch. That should be resolved in the latest beta file: https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/gsap-latest-beta.min.js You should be able to not only use endArray, but also animate individual indexes. 👍
  7. I believe the main problem here was: // BAD! new gsap.timeline() // GOOD gsap.timeline() // don't use "new"
  8. It should actually be pretty easy - you just put your animation code into a function that you call initially as well as onresize. Store a variable for the timeline outside of that function. Record its position and re-set it on the new stuff so it all feels seamless. Pseudo code: var tl; // timeline function buildAnimation() { var time = tl ? tl.time() : 0; if (tl) { tl.kill(); } tl = gsap.timeline(); tl.to(...) .to(...); // do your animation tl.time(time); // set the playhead to match where it was } buildAnimation(); //kick things off window.addEventListener("resize", buildAnimation); You can invalidate() a timeline anytime - that'll force it to re-record its starting values on the very next render. Feel free to do that in an onRepeat if you'd like (or whatever).
  9. Another benefit is that you can use function based values. And it fits with keyframes and makes the code more readable/clear. Trust me - it's a little annoying at first for people who are very used to the "old" way, but I'm pretty confident you'll grow to appreciate it after a while.
  10. GreenSock

    gsap3 crash

    Sorry to hear about the problem, @jonForum. It's super difficult to troubleshoot blind - can you provide a reduced test case? I really need to be able to see the problem in context. It kinda sounds like there's an issue with the target that you're feeding in (just a guess).
  11. Ah yes, again, I was showing you each suffix, _short, _ccw, and_cw. If you want the behavior you described, just make them all _short. I can't imagine how else it would interpret 370. I've never seen an engine that refuses to accommodate any values outside of the 0-360 range. For example, -30 is valid, as is 370 or 720 or whatever - they're all just rotational values. I'm pretty confident it'll work perfectly, but let us know if you find otherwise. Happy tweening!
  12. Yes, that's by design - a rotation of 370 is identical visually to 10. It snaps at the end to ensure that it matches the end value you entered, but there's no reason to do the extra calculations with a modulus operator on every tick (at least not from what I can see). Am I missing something? That's because I put "_ccw" (counter clockwise) on that one, just to show you what's possible. So it's doing exactly what I told it to do. you can change that to end in "_short" if you want it to just choose the shortest direction. Was that a typo? You told the tween to animate to 350, but you want it to actually go to 359 and instantly jump back to 350? I assume it was just a typo and this tween was doing what you expected, right? Again, I don't see any problems with the way it's behaving now, so please help me understand the issue.
  13. Why "not quite"? What isn't working the way you expected? From what I can tell, it's working perfectly in your tests.