en en en en en en en en en en en en en en en en fa en en fr hbs_lat en en en es en en en ms en de en fr en en en ca en en en en en en en es es en en de en en en en en en en en en en en en en en en en en en en en en en en en en en de en en en en en en de en en en es en eu en en en de en en en de en pt en de en en en en en en en en en en en fr cv es tr es en en en en ms en en en en en en fr en hbs_lat en en en en en en en fr cv es tr es en en en en de en en en ca en en en en en
I tried to search where I could before posting, but I don't know how I missed that. Thanks for the information!
Change a draggable element's boundaries after being set
Jeffrey posted a topic in GSAP
Extend hitTest functionality to all of GreenSock?
Jeffrey replied to Jeffrey's topic in GSAP
I think those are interesting ideas. As far as it not being integrated with TweenMax - and instead using one of the other approaches you mentioned - I'm not particular on that. Maybe having collision detection be another plugin might be a good solution? Any way you choose to pursue it, I look forward to this becoming part of the library. I know it will open a great deal of potential for me as I continue to use it in my products.
Extend hitTest functionality to all of GreenSock?
Jeffrey posted a topic in GSAP
I've been playing around with the new hitTest functionality this morning, and I have to say it's pretty fantastic and elegant, which is ideal. I'm wondering, though, if this same functionality can be extended to TweenMax to work with any GreenSock functionality and not just draggable. What I'm wanting to do is move elements around with the keyboard (or really any event) and be able to simply detect whether two or more elements are overlapping without that element having Draggable invoked on it. I've currently been writing my own collision detection engine to accomplish this, but being able to do it with a simple hitTest check would be far, far preferable, particularly as it would be elegantly integrated with GreenSock. As a simple example of one thing I'm doing right now: I invoke an animation which uses 3D transforms to move an element, and when that occurs I'd like to be able to do a simple check to know if during that animation the element collides with another, and allows me to then invoke another function at that point (such as stopping the animation). It would also be great if it could detect specifically which side of an element it collides with (left, top, right, bottom).
“Sincerely, the people behind GSAP are sorcerers”
“GSAP and CSS Transitions: I've done both, and its like comparing an F16 to a horse. Take like 10 minutes to try.”
“I can definitely say ever since I started using GSAP, my work exponentially improved. It basically changed my life.”
“The depth of GSAP blows me away like all the time. It seems like I stumble on something new and amazing every time I peek at the docs.”
“@greensock it’s a great library that many people love, and I know you care deeply about performance :)”
“I continue to be astounded by the sheer breadth of what @greensock can do. Every time I'm like "ooh, I wonder if I can do X", it turns out I can!”
“I've never worked with a product that has such fantastic and enthusiastic support. GreenSock is incredible in its own right, but the team behind it is really what makes it shine.”
“Every time a new GSAP plugin is introduced, I'm close to bursting from excitement. The simplicity of the GreenSock API makes learning and applying these tools in projects such a dream.”
“@greensock is just pure awesomeness. What more can be said?”
Sign Up For Our Newsletter
Get the latest updates on GreenSock products, exclusive offers, and more right in your inbox.
Your information will always be kept confidential.
Thanks for signing up!
Now you'll begin receiving the latest GreenSock updates, exclusive offers, and more right in your inbox. Welcome aboard.