Skip to content

Conversation

@iamwhosiam
Copy link

@iamwhosiam iamwhosiam commented Oct 13, 2025

This is kind of the dumbest solution to a feature that I would like in cute_aseprite. When it is compiling all of the layers together, it would be nice if there was some sort of option to not deref the color palette. I am using the image in indexed mode and it seems like a waste of cpu time to recompile the frames if it just got done looking up all of the palette colors. It also changes the api which isn't good. But I can't think of a better way to do it.

Edit:
Other solutions would be to wrap the behaviors in an ifdef? This would make it so you couldn't do both in a project.

Another way would be to add a cute_aseprite_load_from_memory_indexed(). This would take a bit more restructuring if you didn't want to just straight up have a complete copy of all of the code.

…compiling frame->pixels

This is kind of the dumbest solution to a feature that I would like in cute_aseprite. When it is compiling all of the layers together, it would be nice if there was some sort of option to not deref the color palette. I am using the image in indexed mode and it seems like a waste of cpu time to recompile the frames if it just got done looking up all of the palette colors.

I don't think this is the best solution, it changes the api which isn't good. But I can't think of a better way to do it.
@iamwhosiam
Copy link
Author

another idea I could do is a cute_aseprite_load_from_mem_ext() that takes a pointer to a function that handles the finalizing of the frames. this could open it up to support other things that people might want to do with the data.

the cute_aseprite_load_from_memory() could just do the default thing that 99.999% of people will be using it for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant