Persistent and Impersistent layers for animation #99

Closed
aseprite-bot opened this Issue Aug 20, 2014 · 3 comments

Comments

Projects
None yet
3 participants

From kirby...@gmail.com on April 22, 2012 21:47:13

What do you need to do? When a new frame is created, the contents of the current frame are always copied to the new frame. I would like the ability to choose which layers are copied and which are not. How would you like to do it? I propose a checkbox in layer properties called "Persistent" or similar. When checked, that layer would be copied to the new frame, and when unchecked it would be drawn transparent on the new frame.

Example: I have a background layer that is checked "Persistent", and a sprite layer that is not. I draw my background on the background layer. I draw an animation frame of my sprite on the sprite layer. When I press "alt+n" a new frame will be created with the background layer copied, but a blank "sprite" layer.

"Persistence" would only affect new frame creation. So I could then edit the background layer on frame 1 without changing frame 2, or edit the background layer on frame 2 without changing frame 1.

Original issue: http://code.google.com/p/aseprite/issues/detail?id=99

aseprite-bot referenced this issue Dec 6, 2014

Open

New Timeline #293

18 of 23 tasks complete

dacap added the timeline label Jan 21, 2015

dacap added this to the v1.1 milestone Jan 21, 2015

Owner

dacap commented Jan 21, 2015

The Frame > New Empty Frame (Alt+B) menu option partially fix this issue. Anyway I don't know if this option could be easily integrated without adding more UI complexity now that a new concept of continuous layers (linked cels) is being implemented:

linked

I opened this issue and I consider the planned continuous cels/new empty frame solutions for it. It can be marked closed if no other users are subscribed to this to voice their want of this exact implementation. No one else had starred the old one on google code.

Owner

dacap commented Feb 17, 2015

dacap closed this Feb 17, 2015

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