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
Issue with copy/pasting on hidden layers #3254
Comments
Hi @KrisysTheFool, what specific version of Aseprite are you using? (You can check the version of Aseprite in the title bar) |
dacap
added a commit
to dacap/aseprite
that referenced
this issue
Feb 26, 2024
…eprite#4179, fix aseprite#3254) This fixes several problems in MovingPixelsState where hidden layers were transformed anyway when we switched the visibility of a layer in this state. Other fix was tried before in aseprite#3254 but we needed the onBefore/After layer visibility change notifications to make this work properly (i.e. drop pixels when the visiblity of a layer is changed). The only drawback at this moment is that changing the visibility of the non-active layer when we are transforming multiple cels/timeline range can be confused because we don't have aseprite#2144/aseprite#2865 implemented yet. This bug was originally reported here: https://community.aseprite.org/t/20621
dacap
added a commit
to dacap/aseprite
that referenced
this issue
Feb 26, 2024
…eprite#4179, fix aseprite#3254) This fixes several problems in MovingPixelsState where hidden layers were transformed anyway when we switched the visibility of a layer in this state. Other fix was tried before in aseprite#3254 but we needed the onBefore/After layer visibility change notifications to make this work properly (i.e. drop pixels when the visiblity of a layer is changed). The only drawback at this moment is that changing the visibility of the non-active layer when we are transforming multiple cels/timeline range can be confused because we don't have aseprite#2144/aseprite#2865 implemented yet. This bug was originally reported here: https://community.aseprite.org/t/20621
dacap
added a commit
to dacap/aseprite
that referenced
this issue
Feb 26, 2024
…eprite#4179, fix aseprite#3254) This fixes several problems in MovingPixelsState where hidden layers were transformed anyway when we switched the visibility of a layer in this state. Other fix was tried before in aseprite#3254 but we needed the onBefore/After layer visibility change notifications to make this work properly (i.e. drop pixels when the visiblity of a layer is changed). The only drawback at this moment is that changing the visibility of the non-active layer when we are transforming multiple cels/timeline range can be confused because we don't have aseprite#2144/aseprite#2865 implemented yet. This bug was originally reported here: https://community.aseprite.org/t/20621
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've noticed over a hundred or so hours that ctrl+c / ctrl+v behaves in a weird and sometimes disturbing way when a hidden layer is selected. Whenever I have an area of the picture selected with the marquee tool, and I've picked a hidden layer in the layer list, pressing ctrl+c or ctrl+v (if I've noticed that correctly, still not entirely sure on the specifics of what happens) will erase whatever is in that area on the hidden layer without putting anything in the clipboard. It's usually not very problematic, but combined with a little bit of fatigue it sometimes leads to a huge load of mistakes :( I would love to see that fixed. Thanks!
The text was updated successfully, but these errors were encountered: