![]() ![]() ![]() I’ve managed to learn so much from that so I’ll always be “GSAP and CSS Transitions: I've done both, and its like comparing an F16 to a horse. It’s been one of the most enjoyable things I’ve ever studied and the team do a fantastic job of making it first of all but also in the fantastic forums. See the Pen YzRwPXz by saulnewbury ( on CodePen Is there an obvious way to do this that avoids this expense? At this point I can't see how to separate that stuff, as the 'if' condition – hypotenuse * 2 < triggerDistance – determines which text element is pulled on by the cursor. So all the calculations for hypotenuse and angle are happening on mousemove, along with querying the DOM. Should they start together in reverse too?Īlso, there is a little more complexity in the max version, in that the magnetic effect acts on both the custom cursor and the text inside the target. I realise the tweens start at the same time going forward but I can't tell whats happening going backwards. Seems to be delayed now, perhaps due to running inside a timeline, in reverse. I've just been modifying my code with your suggestions in mind and I've hit a wall with trying to get the scaling of cursor-outline to animate on mouseleave, in the way that it did before. Love the simple/nifty approach to scaling. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |