TweenGMS 2 Beta 4.1
TweenGMS » Devlog
This is a small update to the larger Beta 4 release. You can find the post for that update here.
This update fixes an issue where TweenEasy*() functions could cause a crash if called immediately at game start. Additional changes are below...
[4.1]
-Fixed issue where starting an easy tween at launch would cause crash
-Fixed TGMS_FetchTween() to properly return undefined/null tween ids
-Adjusted TGMS_FetchTween to prevent crash if o_SharedTweener doesn't exist yet
-Stopped adding "TGMS" layer to rooms
Get TweenGMS
TweenGMS
Tweening engine for GameMaker
More posts
- TweenGMX Beta 14 + Moving to GM MarketplaceJul 24, 2022
- TweenGMX Beta 13 (Essential Runtime Fix)Jun 24, 2022
- TweenGMX and Beta 12Apr 18, 2022
- TweenGMS 1.20 "Silent" UpdateApr 02, 2022
- TweenGMS v1.20Mar 30, 2022
- TweenGMS Pro v1.12 (copy-on-write fix)Feb 25, 2022
- TweenGMS 2 Beta 11Feb 07, 2022
- TweenGMS Pro v1.11Jan 01, 2022
- TweenGMS 2 Beta 10Dec 28, 2021
- TweenGMS Pro v1.10.1 (Small Fix)Dec 01, 2021
Comments
Log in with itch.io to leave a comment.
bug report (and workaround for it):
struct property tweening (such as TweenFire(apple, EaseLinear, 0, true, 0, 5.0, "x>", 50);) didn't work for me in this release until i made the following change to the function TGMS_Variable_Get in TGMS_7_Properties:
if anyone else if having this issue, make this change and it'll start working. the change is adding "and !is_struct(target)" to the if statement. this might not be a proper fix though so hopefully an update fixes the issue
Hey!
I'd like to confirm your example....
TweenFire(apple.x, EaseLinear, 0, true, 0, 5.0, "x>", 50)
The first argument [apple.x] should just be [apple]....
TweenFire(apple, EaseLinear, 0, true, 0, 5.0, "x>", 50)
Structs are quite a new thing, so expect there to still be issues. I appreciate this being brought up. I can check and verify these things later.
I am writing this from my phone, so sorry if this text comes out messy :)
oh my bad, i got confused with the syntax when i wrote that post, just was trying to think of an example. but here's what i had that wasn't working (where _element is a struct like { x: 0, y: 0 }):
this doesn't work and gives me this error:
but if i make the change i described in my post, it works.Thanks! I might look into this more tonight.
Thanks for the help!
I was able to clean things up which hopefully will make things more stable overall.
The latest blog post mentions a couple other additions to the update.