Jump to content
GreenSock

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

GreenSock last won the day on October 21

GreenSock had the most liked content!

GreenSock

Administrators
  • Content Count

    13,502
  • Joined

  • Last visited

  • Days Won

    418

Everything posted by GreenSock

  1. Yeah, it's just a JavaScript thing. When you this.props.dispatch(setColor('#1b00ff')), that runs it immediately because the () act as an instruction to invoke the function. You just need to wrap it in a function: .call(function() { this.props.dispatch(setColor('#1b00ff')) }, null, this, '+=2') You were missing the params parameter too. https://greensock.com/docs/v2/TimelineLite/call() Does that clear things up?
  2. Sure, like this?: https://codepen.io/GreenSock/pen/zYYoXmR?editors=1010
  3. Hi @Xristi. Would you please provide a reduced test case codepen that illustrates the issue? I'm not totally sure I understand what you're asking. Also, in general it's best to create a new thread for questions like this rather than hijacking an old thread, but I know you were referencing the example above and that's probably why you thought it'd belong here. Not a big deal.
  4. For the record, I wouldn't expect GSAP 3 to deliver any noticeable gains in this animation because by FAR the biggest drain is the rendering load on the browser which is totally unrelated to GSAP. In other words, GSAP's work may account for less than 1% of the overall load on the browser, so even if GSAP was TWICE as fast (it's not), you'd only see a 0.5% increase in overall performance. But yeah, like @ZachSaucier said, there's a lot about GSAP 3 that could be useful to you, especially the utility methods. 👍
  5. You should always use the ScrollToPlugin for scrolling because there are various differences among browsers. For example, in many browsers you can't set the scrollTop property on the window element - you literally must call window.scrollTo() method. GSAP's ScrollToPlugin handles all that for you.
  6. Thanks for the additional info, @Martin Shuttleworth TM! Would you mind trying the (updated, uncompressed) beta file?: https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/Draggable-latest-beta.js
  7. Hm, sounds like maybe a yarn problem, @nolafs - I'm not quite sure what to tell you. Did you try yarn cache clean dep ? Did you make sure you have a "./" on the front of the path? I read that yarn can have a problem with local dependencies. You could also try something like yarn install file:./gsap-bonus.tgz
  8. @Martin Shuttleworth TM so onRelease fires twice on the same Draggable in quick succession? Does the onPress fire multiple times as well? It's odd because there's code in the onRelease that checks isPressed and if it's false, it skips the onRelease altogether, and if it's true, it immediately sets isPressed to false (and does the onRelease). So something sound very strange here. I'm eager to see the reduced test case. A codepen would be ideal.
  9. Hm, I just can't seem to reproduce this - can anyone provide a reduced test case? Anyone??? I assume you're using the latest version, and tried the beta as well, right?
  10. Welcome the forums (and GSAP)! The problem is just that TweenMax.staggerFrom() returns an ARRAY of tweens....and you're trying to call play() on an array instead of on an animation instance. If your goal is to control a group of tweens, you should definitely be using a TimelineLite or TimelineMax. Those have their own staggerFrom() method that does exactly the same thing as TweenMax.staggerFrom(), but puts all the resulting tweens into a timeline wrapper that you can then control very easily. Here's a forked demo: https://codepen.io/GreenSock/pen/ea091b3374c3372e2e49bd77a1f16131?editors=0010 I'd also strongly recommend reading this article: https://css-tricks.com/writing-smarter-animation-code/ Happy tweening!
  11. I don't notice an obvious problem with your code, so there must be something else going on - can you please provide a reduced test case? It's difficult for us to troubleshoot without seeing the problem in context. Do you perhaps have an earlier animation that's infinitely repeating or something that'd push the "endSubSlideOut" waaaaaay back in the timeline so that the playhead isn't hitting it for a LOOOOONG time? Are there any errors in the console?
  12. You don't need a Club GreenSock membership for TweenMax to work. That's only if you need the bonus plugins, none of which are essential for most animation. Certainly not for what you're doing. There must be something else going on with your page on the live (non-codepen) version.
  13. Yeah, it's pretty tough for us to troubleshoot blind. If you still need help, please provide a reduced test case that shows it "broken" and we'd be happy to take a peek.
  14. GreenSock

    Cobo

  15. Yes, I just uploaded a new zip that you can grab from your account dashboard. Enjoy!
  16. Welcome to the forums! It looks like TweenMax is doing exactly what you're asking it to do (move the element with the class "PlayStationPlus" to the right by 600px). I'm pretty lost as to what exactly you're trying to do and why you think TweenMax isn't working. It looks like you've got a bunch of CSS animations applied to various elements. I'd suggest maybe starting with a much simpler setup, get an element or two animating, and then building on that. If you're still having trouble, could you please give us more info about exactly why you think TweenMax isn't working and what you're trying to do? A much simpler Codepen would also be very helpful. We'd love to assist you...I'm just not sure what you're asking.
  17. @knalle sorry about that! It was a very obscure (unknown) bug that'd only happen in very rare situations, and of course yours triggered it. Glad it got exposed. I just applied a fix and uploaded a new codepen-only file: https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/MorphSVGPlugin.min.js If you clear your cache, you should see that it's fixed. Better?
  18. @Santoriello @chris_hengst Any chance you could provide a reduced test case with just the most basic setup to demonstrate the issue? I've been poking around various demos on my iPhone with iOS 13.1.2 and things seem to be working great for me. I'm sure I'm missing something, so any help you could provide in terms of a simple demo, I'd sure appreciate it. Oh, and as for your old fix (that doesn't work in iOS 13), have you tried adding a "touchforcechange" event listener (and calling preventDefault() on the event)?
×