WIP Directionality function addition.

[Loufe]

WIP, not yet tested.

This PR aims to add the ability to supply a "type" of animation as well as a Vector2 rather than the entire animation name, as an option.

How it accomplishes it:

Play command modified to be as flexible as possible:

• Current usage approach maintained (LPCAnimation as sole parameter).
• Rather than an LPCAnimation, String now works (type checking for "animation" parameter)
• Can send only a string of type and existing facing Vector used.
• Optionally, send a facing Vector with String of type to set new animation at that direction.
• Optionally, supply true for last parameter for precompiled oversize.

Some notes with the PR.

• Requires a copy of Array[LPCAnimation] in LPCAnimatedSprite2D (will follow system established here https://github.com/alextrevisan/LPCAnimatedSprite2D/pull/21) to perform lookups. This does not require valid column, row numbers - only valid "name", "type", "direction" fields - so we can ignore oversize issues with compiled setups.
• The LPCSpriteData is modified to include two extra fields: "type" a string of the type such as "CAST", and "direction" a Vector2 corresponding to _UP, _DOWN, etc.
• My "cur_dir variable" approach will be rewritten (ran out of time). I got the lookup working afterwards so this may now be the way current direction is looked up rather than maintaining a parallel representation. Open to keeping it, though. I was forgetting, cur_dir is requires as compiled sheet setups won't have each array element doing the current animation. Might be possible, but would not be elegant.
• I put a lot more effort this PR to think of compiled sheet setups, please let me know if I missed any.

Let me know your thoughts.

Hopefully will have an hour tonight to do some required changes.

[alextrevisan]

Just for simplification, all Vector2 can be one of:

Vector2.UP Vector2.DOWN Vector2.LEFT Vector2.RIGHT

They are just constants for the vector, but I think the code will be clearer. What do yout think?

[Loufe]

Just for simplification, all Vector2 can be one of:

Vector2.UP Vector2.DOWN Vector2.LEFT Vector2.RIGHT

They are just constants for the vector, but I think the code will be clearer. What do yout think?

I'm learning a little more every day 😅 great point. We can clean it up in the precompiled branch later on.

Are you ok with adding those parameters to LPCSpriteData ?

[Loufe]

With latest commit this is working on my end. Already makes code in my project (adjustments for testing) a lot cleaner.

@alextrevisan , If you have time to test and review I'd appreciate it.

[Loufe]

I'll try again soon with a fresh PR, no use keeping this old base one alive.