Jump to content
GreenSock

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

GreenSock last won the day on January 15

GreenSock had the most liked content!

GreenSock

Administrators
  • Content Count

    13,861
  • Joined

  • Last visited

  • Days Won

    442

GreenSock last won the day on January 15

GreenSock had the most liked content!

Community Reputation

9,072 Superhero

About GreenSock

  • Rank
    Administrator

Contact Methods

Profile Information

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

Recent Profile Visitors

50,038 profile views
  1. GreenSock

    Laggy animations

    @PaulB yes, I definitely want to see a reduced test case if at all possible because GSAP 3 should not be noticeably slower than GSAP 2 and I'm very curious to see your use case. Do you have a reduced test case that shows v2 and the same thing with v3 that we can compare? I wonder if the perceived difference actually has nothing to do with GSAP but only a change in the way certain browsers render things. I remember a while back Chrome suddenly changed how it rendered 3D transforms (at least on the Mac) and it made a HUGE performance difference but nothing changed in GSAP.
  2. I think Zach already answered that above - you must have a license for anyone who writes or edits any GSAP-related code in your theme/app/site. Yes, if the developer that has the license creates something for another company that sells it but NOBODY (besides the license-holder) makes any edits or codes anything that's GSAP-related, that's fine. It's not a license that can be passed around though. I think you'll find that the license pays for itself quickly, even if you need to get a multi-developer license. Happy tweening!
  3. GreenSock

    The locomotive

    Sorry about that, @mikel - there was a regression in 3.0.5 that caused tweening of timeScale() on another animation not to always work as expected. That 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 - is that better?
  4. Yeah, that's because the official GSAP property is "rotation", but when you directly animate things via CSSPlugin it'll accept some aliases too like "rotate" (which internally we just map to "rotation"). MotionPathPlugin wasn't able to do that mapping. I'll update the next version of MotionPathPlugin to look for those aliases too - here's a preview: https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/MotionPathPlugin.min.js Better? By the way, thanks so much for the reduced test case! Super helpful.
  5. @ZachSaucier that's because there was literally no color applied at all, so it's treated as transparent. Here's a simplified version that seems to work for me (unless I'm misunderstanding the goal): https://codepen.io/GreenSock/pen/mdyzBXN?editors=0010 There are actually a ton of other ways to do this, @shanemielke. Does the above example work well for you or would you like some other options? You probably don't need an onUpdate, though that's perfectly acceptable if you prefer to go that way.
  6. GreenSock

    Access svg outside.

    I'm a little lost about what exactly you're asking here or what you need help with. And it's super difficult for us to troubleshoot blind - if you still need some help, can you please provide a reduced test case that shows the issue? Otherwise we're just grasping at straws. You definitely shouldn't be mixing GSAP animations with CSS transitions. Remember, CSS transitions kick in ANYTIME a property is changed and since GSAP literally changes the values about 60 times per second, the CSS transition would basically interrupt every time and say "WAIT! Don't make that change quite yet...I'm gonna slowly do that.", thus you get conflicts. See what I mean? I can't imagine a scenario where it'd be helpful to mix CSS transitions and GSAP animations, so maybe you can describe why you did that (what your goal was) and we can help you go in a better direction.
  7. Without seeing a reduced test case, my best guess is that you just forgot to register Draggable. gsap.registerPlugin(Draggable); (Obviously do that before you actually use Draggable) Does that help?
  8. Sure, you could simplify that quite a bit. Here's a fork with GSAP 3: https://codepen.io/GreenSock/pen/f960d221c5f4074d7c7ae3965edafa07?editors=0010 Is that what you're looking for?
  9. Actually, the next release has a tweak that automatically handles this for you, so you can simply align: "#path". I've already updated the live codepen version of MotionPathPlugin which you can see in the last demo I posted.
  10. I'm curious why you'd want to move to Flash. It's a pretty dead technology. We haven't actively supported our Flash-based tools for many years. You're welcome to use them, of course, but I'd personally recommend being very cautious about moving your project to Flash.
  11. @jollygreen I'm totally confused. Can you show us an example of that? I can't imagine how that'd work. Like @Shaun Gorneau said, "visibility" isn't an animatable property (what would the halfway-between value be exactly? visibility: "kinda"? ) I'm sure we're just misunderstanding something about what you're saying/wanting, so it'd be super helpful to see a reduced test case, perhaps in codepen? And why exactly are you NOT wanting to use autoAlpha? The entire point of that special property is to handle both opacity and visibility for you. So it seems perfect for the effect you described, but again, I must be missing something.
  12. Okay, so the issue here is that even though you set border-radius in your CSS, getComputedStyle() in Firefox reports it as blank! I'd certainly consider that a bug in Firefox. In the next GSAP release, I work around this by sensing that condition and then pulling the value from borderTopLeftRadius. It seems to work well. Feel free to try it for yourself in the beta file: https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/gsap-latest-beta.min.js Better?
  13. I actually think that might compound the problem because: The minified files would technically be different than all the other files with those same names, like the ones that reside on the CDN. The path to the map file would be different...so it'd be weird to have two files with identical names and are the same version of GSAP...but contain different contents. My understanding is that it's a widely-accepted convention to keep the .map files with the files they describe (same directory) It'd add yet another folder to the zip, making it potentially confusing/intimidating for users to understand which things they need and which folder(s) to use. I'm inclined to just stick with the convention we're using everywhere else (including on the CDN) and have the map files reside with the minified files.
  14. Actually, all you need to do is set useRadians: true in your motionPath vars. Sorry, we're still working on the docs, so not everything is there yet. But this should make it pretty easy for you - no proxy necessary. https://codepen.io/GreenSock/pen/bGNjpKo?editors=0010
×