New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Layer groups / folders #454
Comments
There is already some work-in-progress for this feature (I think it will appear on v1.2 beta2). |
Implemented, this will be included in the next v1.2-beta2 |
@dacap super! Will you also include a subfolder as a parameter for aseprite cli for |
@nakedpony I'm still thinking about this (as well as the Export Sprite Sheet when "Selected layers" are chosen). I think this is highly related to #1174 |
Maybe something like |
I guess it makes sense to be able to filter out layers/folders by by index as well as by name if I understand correctly your approach in #1174 and with folders. |
I was thinking and they are two different things. #1174 talks about a way to filter layers by name (I still need a syntax children, e.g. The other one is about Anyway I'm not yet sure about this |
Oh, I see now. You want to introduce multiple nesting of the layers. So I think that selecting layers could be as you described. And I guess As for format when importing deep nested structure of layers... Let's look at the variants:
|
@dacap BTW it would be a huge improvement if every layer could be exported separately to multiple tags aka animations to unity format. Similar to this script https://github.com/talecrafter/AnimationImporter but splittable by layer. Just a task I'm struggling with at a moment. I guess it could make aseprite even more popular and easy to use :) |
@nakedpony about the improvement "if every layer could be exported separately to multiple tags," I'm not sure if I understood this correctly, but actually on v1.2-beta1 you can use something like:
Or maybe you want all frames of each "layer+tag" combination in one
(Not yet implemented.) |
About the group identifiers, I've found an alternative:
I'll just add |
I'm implementing this and more tricky scenarios are appearing. For example, if we have this structure: We might try to use:
In this case, I'm sure that this should generate at least 4 files:
But I'm not quite sure about the other layers (the groups). Should it generate the following files?
Or these other files?
I think that in this case it should generate 4 files and nothing else. And if we use the following command:
It generates the following files:
There are a lot of tricky combinations and I'm not so sure what to do on each case. I'll thinking more about this and try to find a "good enough implementation" for the first version. |
going to take a look at this thread later tomorrow :) |
it's more than enough for me for the first version :) |
There is a part of this issue that wasn't yet implemented and I'll try to implement for v1.2-beta3, #1238 |
I want layer group like Photoshop.
I'm sure It's useful for pixel art too.
for example
2 layers in 1 group.
upper Body(group)
|--Body(layer)
|--Arm(layer)
then you can manipulate 2layers at once.
(select human group ->select some region->You can transform(move,rotate,etc) Body and Arm layer at once.)
Thank you.
The text was updated successfully, but these errors were encountered: