[Feature Request] Add an option --ignore-layer <name> to the CLI #1264

Closed
talecrafter opened this Issue Sep 22, 2016 · 5 comments

Comments

Projects
None yet
2 participants
@talecrafter

Would be great for my personal workflow to have an option of ignoring a specific layer when exporting to PNG+JSON.

My use case is this:
I use one Layer with meta informations where neon colored pixels mark offsets. (The image is analyzed later in the pipeline.) I need this layer to be visible while working in Aseprite but the automated processing needs that layer separated from the other layers. My plan would be to call the CLI once with --import-layer to just get the meta layer, and then once with --ignore-layer to get the rest of the image.

I can think of workarounds (including the nuisance of toggling it manually before exporting), but if it's not much work it would be great to have it in there. Maybe it's also useful for other people building their automated workflows.

@dacap

This comment has been minimized.

Show comment
Hide comment
@dacap

dacap Sep 22, 2016

Member

Hi @talecrafter, I think it's a good idea. I'll try to include this in the next beta.

At the moment, in v1.2-beta2, you might try to use two groups, one for mark/guides, and other group for the sprite itself, then you can ignore marks using --layer groupname (or --layer groupname/* to make visible all children in that group and hide all other groups).

Member

dacap commented Sep 22, 2016

Hi @talecrafter, I think it's a good idea. I'll try to include this in the next beta.

At the moment, in v1.2-beta2, you might try to use two groups, one for mark/guides, and other group for the sprite itself, then you can ignore marks using --layer groupname (or --layer groupname/* to make visible all children in that group and hide all other groups).

@dacap dacap added the enhancement label Sep 22, 2016

@dacap dacap added this to the v1.2 milestone Sep 22, 2016

@talecrafter

This comment has been minimized.

Show comment
Hide comment
@talecrafter

talecrafter Sep 22, 2016

Excellent. Thank you.

Excellent. Thank you.

@dacap dacap self-assigned this Sep 23, 2016

@dacap

This comment has been minimized.

Show comment
Hide comment
@dacap

dacap Sep 23, 2016

Member

This is already available in the new Aseprite v1.2-beta3

Member

dacap commented Sep 23, 2016

This is already available in the new Aseprite v1.2-beta3

@dacap dacap closed this Sep 23, 2016

@talecrafter

This comment has been minimized.

Show comment
Hide comment
@talecrafter

talecrafter Sep 24, 2016

When using this command line option, hidden layers get exported too. They get not exported when not using this option. I assume that's a bug and not intended behaviour.

When using this command line option, hidden layers get exported too. They get not exported when not using this option. I assume that's a bug and not intended behaviour.

@dacap

This comment has been minimized.

Show comment
Hide comment
@dacap

dacap Sep 24, 2016

Member

It is a bug :( I've created some unit tests for this but I need to test it more with files with a mix of hidden/visible layers. Reopening the issue.

Anyway, I'm thinking that I might give more priority to batch export using projects #126 or post-save hooks #138

Member

dacap commented Sep 24, 2016

It is a bug :( I've created some unit tests for this but I need to test it more with files with a mix of hidden/visible layers. Reopening the issue.

Anyway, I'm thinking that I might give more priority to batch export using projects #126 or post-save hooks #138

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