-
Hey guys, I recently update flixel from 4.11.0 to 5.3.1 and tried to run an old project, as expected I got some errors and warnings, but I don't get some of them:
Can someone help me? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
I recommend upgrading to flixel 5.0.0 first, using this 5.0.0 migration guide. Once you've done that, then you should be able to jump to 5.3.1. as for you're specific error, it's outlined here in the migration guide, and the fix is simple: Replace static calls like Once you're on 5.0.0, you should only have deprecation warnings, and you can either ask about them here or check the changelog for details |
Beta Was this translation helpful? Give feedback.
I recommend upgrading to flixel 5.0.0 first, using this 5.0.0 migration guide. Once you've done that, then you should be able to jump to 5.3.1.
as for you're specific error, it's outlined here in the migration guide, and the fix is simple: Replace static calls like
FlxMouseEventManager.add(...)
with calls toFlxMouseEvent.add(...)
. We added a default mouse event manager, similarly to how FlxTween and FlxTimer work.Once you're on 5.0.0, you should only have deprecation warnings, and you can either ask about them here or check the changelog for details