piskel icon indicating copy to clipboard operation
piskel copied to clipboard
verified publisher icon piskelapp

[Feature] - add duplicating layers, creating layers from select and copy/pasting of layers

Open Qudios opened this issue 11 months ago • 2 comments

Wonderful Software, I do believe:

  • being able to duplicate layers would speed work by a lot

  • creating layers from what you rectangle/lasso select would be very nice instead of having to copy/paste selected into a new layer

  • copying/pasting layers would also avoid the need of rectangle selecting and pasting into a new layer

  • Is it possible to make the Layer System Independent depending on the frame? like I should be able to change the opacity for a layer only for a frame or delete a layer only for a frame instead of apply to all.

Qudios avatar May 06 '25 01:05 Qudios

BLUF: I think implementing macros is a better solution. However I have no idea how hard this would be.

This feels like two issues.

  1. Layer duplication.
  2. Independent layer properties.

I'm conflicted about independent layer properties. Needing to set the opacity of every single frame would be very annoying. It feels like we're exchanging one problem for another. A key frame system could be nice, but that feels like a significant overhaul.

The ability to duplicate layers would be helpful, but I wonder if this gets to a deeper issue. I think it would be good if we could implement macros. Duplicating a layer is essentially a sequence of actions:

  1. create new layer
  2. copy selection to new layer
  3. repeat for all frames

If this was a new feature, the behavior is fixed. If this was a macro the user could choose to omit step 3 if they only wanted to duplicate that one frame layer.

Another example: If I wanted to fade something in (e.g. vary opacity of an object) it would be relatively simple with a macro:

  1. create new frame
  2. create new layer
  3. copy selection to new layer on new frame
  4. increase/decrease opacity of new layer
  5. repeat as many times as I want

Piskel already maintains a history of actions for undo/redo purposes. I bet that could be leveraged to "record" a macro.

enykwest avatar May 06 '25 13:05 enykwest

Yes, Macros would help a lot I feel most of my "issues" or feature requested are generally just making a sequence of actions easier to speed up creation

Qudios avatar May 06 '25 14:05 Qudios