karld Posted November 22, 2019 Share Posted November 22, 2019 I used the auto-detection of getters and setters to tween certain numbers, which I got the idea to do from this forum post However, this no longer seems to work in GSAP 3. Any ideas? Broken in GSAP 3: Working in GSAP2: See the Pen jOORZbM by karldougie (@karldougie) on CodePen See the Pen vYYMdEb by karldougie (@karldougie) on CodePen Link to comment Share on other sites More sharing options...
OSUblake Posted November 22, 2019 Share Posted November 22, 2019 Just use real gettters and setters. See the Pen 2861d5c51d92622b81ab268e7656993f by osublake (@osublake) on CodePen 1 1 Link to comment Share on other sites More sharing options...
karld Posted November 22, 2019 Author Share Posted November 22, 2019 Beautiful! Thanks @OSUblake! Link to comment Share on other sites More sharing options...
GreenSock Posted November 22, 2019 Share Posted November 22, 2019 Yep, here's another option (same general idea): See the Pen 64913f1ea7154fe340abf33e7e3861e5?editors=0010 by GreenSock (@GreenSock) on CodePen The whole thing about methods that start with the word "get" or "set" seemed kinda old-school and I didn't think it was worthy of taking up kb in GSAP 3 since you could so easily accomplish it in other ways. Sorry if any of that was confusing. 2 Link to comment Share on other sites More sharing options...
karld Posted November 22, 2019 Author Share Posted November 22, 2019 @GreenSock I think it is great to move towards standard javascript syntax, and I'm really happy with the reduced size of GSAP! 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now