Cannot paste printscreened things into Aseprite (Regression?) #1122

KasumiArai opened this Issue May 7, 2016 · 2 comments


None yet
2 participants

KasumiArai commented May 7, 2016

This is an unusual one. When I paste an image copied to the buffer with the print screen key, I just get a fully transparent screen, but the dimensions are correct.

Here is a gif
I draw a smiley face, then copy it. Create a new document (you can see that the new document's size is 32x32, the size of the face.) I paste the face. Then I press printscreen. I create another new document. (You can see the dimensions are now 1920x1080, my monitor's size.) I press printscreen on the new document dialog as well. I paste. It's just blank. Then I click Aseprite v.0.9.5, create a new document and paste it there successfully.

The last version I can paste a printscreen in (that I have) is I have a gif of me trying the same paste in, 1.1.5,, and I can send if needed, but it ended up being nearly 4MB. Regardless, only works.

Just for clarity reproduction steps for me are simply:

  1. Press print screen (or alt+print screen)
  2. Paste.

A selection will be created of the right size, but with fully transparent pixels.
Aseprite 1.1.5.X on Windows Vista 32bit.

@dacap dacap added bug critical labels May 7, 2016

@dacap dacap self-assigned this May 7, 2016

@dacap dacap added this to the v1.1 milestone May 7, 2016


dacap commented May 7, 2016

Hi @KasumiArai, this bug is already fixed in my local copy (originally reported here: It's a regression introduced when we switched the clipboard management to the clip library to support OS X copy/paste.

The problem only appears when Windows is running on 32bpp. It's because Windows doesn't include alpha/transparent information in the image. If you paste the image on MSPaint, copy it again, the image is converted to 24bpp an then you will be able to paste the screenshot on Aseprite.

Reference commit 160418d

Good to hear! I was worried it was some weird thing with my PC setup.

@dacap dacap closed this May 10, 2016

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