Describe the bug
Explain the bug as clear as possible, no code involving.

The Sample crashes on startup from the git version

Adobe Animate Version
Adobe Animate version [2022].

Additional context
Add any other context about the problem here.

Describe the bug
While I was testing around some stuff with FlxAnimate I found out that the same symbol renders differently from two different Animate CC versions.

Explain how to recreate the bug
Might not work with all symbols, but export a texture atlas from Animate 2019 & 2021 and display them using the following code:

var animTest:FlxAnimate = new FlxAnimate(50, 50, "[Path]", {Antialiasing: true});
animTest.anim.addBySymbol("a", "[Symbol Name]", 24, true);
add(animTest);

animTest.anim.play("a");

What should happen?
The symbols should display identically.

Adobe Animate Version
Animate CC 2019 19.2.1 (build 408)
Animate CC 2021 21.0.6 (build 41649)
FlxAnimate version is the one from Haxelib

Additional context
How it displays when exported from Animate 2021:

How it displays when exported from Animate 2019:

Files for both texture atlases
2019: https://cdn.discordapp.com/attachments/1006517991531368558/1033747631295443005/halloween_oceanrant.zip
2021: https://cdn.discordapp.com/attachments/1006517991531368558/1033747631685509223/halloweenAn21.zip

I can also provide the fla if it can help out with debugging.

Describe the bug
When creating an FlxAnimate object with a library in the path (eg. coolstuff:assets/coolstuff/atlas_1) the game closes instantly without an error message or anything.

Explain how to recreate the bug

1. Create a new FlxAnimate object with a path that contains a library (eg. coolstuff:assets/coolstuff/atlas_1)
2. Game closes

What should happen?
The FlxAnimate object should be created without any issues.

Adobe Animate Version
Animate 2019 (19.2.1 build 408)

Additional context
I've verified that the path actually exists with OpenFl.Assets.exists() and it returns true, so I don't know why FlxAnimate closes the game.

the Unoptimised texture atlases and have more than one spritemap have issues when finishing in the thing.
Should research more about it

Currently the only way to adjust the size an atlas sprite is rendered at is to export a new atlas at the correct size. The scale attribute does nothing.

Either scaling relative to the sprite's center or to the pivot point would be fine.

There's about 3 filters in Adobe Animate that you cannot support due to OpenFL not having the following shaders implemented:

• BevelFilter
• GradientGlowFilter
• GradientBevelFilter

With some knowledge of GLSL and with the implementation of the dev branch, it would be possible, at least with the BevelFilter
altho with the Gradient ones, I don't really understand how would this work exactly
Maybe create a gradient bitmap and with that doing some shenanigans?
That would be the only way in theory

I know what's the issue and I fixed it in my own build
But I'm making an FNF currently and I'm making the changes while doing the shit and idk if make the commits now or in a few days lmao.
But ye, wanna record this

Currently, FlxAnimate does not have an accurate hitbox (in fact, it does not have a hitbox at all I believe). This can lead to issues with positioning and other stuff dependant on the hitbox.

Describe the solution you are proposing

In theory it should be simple to fix this, although in practice it may not be as simple, depending on how FlxAnimate handles rendering and stuff.

When a frame change happens in an animation, FlxAnimate should get the lowest and highest x and y positions of the currently rendered sprites. From there we have the size of the hitbox and we just need to position it.

I have already attempted to prototype this but tbh I have no idea how FlxSprites hitboxes are created and positioned so my attempt, while working, started dropping FPS because of the goofy method I used to position them.

if you have multiple frames for one animation and the play function only plays one frame, how would you play all the frames, i don't get it here do i somehow have to count each frame then make a for loop which i play that frame inside the loop or what? i don't get the point of making it play a SPECIFIC frame

flxanimate/frames/FlxAnimateFrames.hx:160: characters 18-20 : Expected )

i dowloaded a mod with this and when i tried to load show's me this error.

Error: C:/haxelib/flxAnimate/1,0,1/flxanimate/FlxAnimate.hx:181: characters 20-28 : flixel.input.mouse.FlxMouse has no field released #

Describe the bug
The animations don't do their thing properly, and if you have an STI, you're fuck up what it should be the normal thing.

Explain how to recreate the bug
Use FlxAnimate and try to add anims or use a texture atlas with STI

What should happen?
The animation should go good and without weird shit

Adobe Animate Version
Any version

The width and height values for atlas sprites are not reported accurately. This makes it hard to determine the size of a sprite and therefore position it accurately.

This is solved by #23.

FPS Drops when FlxAnimate is destroyed. Perhaps it's the children still being rendered and not destroyed properly. I was able to fix this in my project so far by using onComplete to remove.

Describe the bug
Compiling any project with FlxAnimate in use produces several compiler errors about the same thing.

Explain how to recreate the bug
For example: Steps to reproduce the behavior:

1. Use FlxAnimate v3.0.3 in any project
2. Compile
3. These errors appear:
   

What should happen?
I'm assuming animations should play correctly, if at all. I don't know for sure what should happen though, since this was in a testing project I made to get the hang of using FlxAnimate.

Adobe Animate Version
Adobe Animate version v23.0

Currently, Filters are going like shit cos when you try to add a filter to one, it adds to every sprite.

My suggestion is actually slice all the sprites and later make the atlas sprite thingies use loadGraphic so that there's an option to make that graphic unique,
Just in case for sprites that don't have filters but have the same sprite don't have the same filter forever.

I'm sorry if it sounds obvious for you guys but I don't know how to export every animation in a single spritemap. If I try to select multiple symbols, there isn't the option.
I need to figure out how to do it so I can put it in my game

Error: C:/haxelib/flxAnimate/1,0,1/flxanimate/FlxAnimate.hx:181: characters 20-28 : flixel.input.mouse.FlxMouse has no field released

Proposal

This enhancement would add the following functions to FlxAnimate:

• getFrame(label:String):Int - Returns the frame number corresponding with a given label.
• goToFrame(label:String):Void - Sets the current frame of the animation to the frame number corresponding with the given label.
• getNextLabel(label:String):String - Returns the name of the next labeled frame, which comes after the label with the provided name.
• addFrameAction(label:String, callback:Void -> Void):Void - Defines a callback function which, after the frame with the provided label is reached, will be executed.
• removeFrameAction(label:String, callback:Void -> Void):Void - Removes a specific callback function from a given label.
• removeFrameActions(label:String):Void - Removes all callback functions from a given label.

Further Documentation

You can see an example of these features in action here:

• https://wiki.starling-framework.org/extensions/adobe-animate#labels
• https://github.com/Gamua/Starling-Extension-Adobe-Animate/blob/755aacd2628a9417405350f17988c7c7cf63339f/src/starling/extensions/animate/Animation.as

Example Use Case

Here is an example use case, copied from the link above.

Assume that you have a character sprite, whose Animate atlas definition contains several animations, including walk, run, crouch, and shoot. Without custom logic, the character would walk for a few frames, then run for a few frames, then crouch for a few frames, and shoot for a few frames, which is clearly not the intended behavior.

Instead, we want to perform some action when the individual parts of the animation complete, like so:

character.goToFrame('crouch'); // Play the crouch animation.
var nextAnimName = character.getNextLabel('crouch'); // Let's say this returns 'shoot'
character.addFrameAction(nextAnimName, function() {
  // When the animation reaches the frame at the start of the 'shoot' animation,
  // loop back to the beginning of the 'crouch' animation.
  character.goToFrame('crouch');
}

The result is that the character can utilize dynamic behavior and animations, without having to rely on swapping between full spritesheets. This saves memory and improves performance.

idk why, but like when I try to compile a simple test project on HTML5 (and Windows I believe!) I get an issue about timeline being undefined,
these are the lines of code i used:
var sus = new FlxAnimate(0, 0, "assets/images/cool", {FrameRate: 24}); sus.playAnim("Ding cool anim"); add(sus);
and this is the error I got:

This issue was spotted on haxe 4.1.4 when they reported this known issue of "FlxAnimateFrames.hx line 165: Expected )" or something like that.

This should solve the issue for everyone that has this issue, altho I'm too lazy to check if that actually should work. I would need someone that has haxe 4 but hasnt got haxe later than 4.2 that can help me with this, or when I have time, downgrade my haxe version myself and fix it

Describe the bug
Changing the angle value of the FlxAnimate object does not affect the game.

Explain how to recreate the bug
Steps to reproduce the behavior:

1. Create FlxAnimate object and add to game
2. Set FlxAnimate's angle value to 30
3. See error, nothing is affected

What should happen?
The angle of the FlxAnimate object should have changed.

Adobe Animate Version
Adobe Animate 2022.

Additional context
Nothing

Adding code to set animation frame to a frame callback sometimes renders the sprite before the callback finishes. If using this technique to loop an animation in an atlas with multiple animations, this can cause the first frame of the next animation to play for a split second before the animation resets.

A workaround exists where adding "padding" frames around animations can help prevent improper frames from rendering, but a proper fix is needed.

The solution may be to add some code which prevents the sprite from being redrawn while a callback is resolving.