How to control the quality/filesize of images copied to the clipboard?

[btse]

@kshegunov said in How to control the quality/filesize of images copied to the clipboard?:

Perhaps I misunderstood then. What I mean is to save that data into the clipboard with your own mime type. Otherwise I believe Qt does serialization/deserialization through a QVariant internally. So try with something like:

QMimeData *mimeData = new QMimeData;
mimeData->setData("image/x-btse-png", bytes);
QApplication::clipboard()->setMimeData(mimeData);

PS:
If that doesn't work, substitute with application/octet-stream and try with it.

I tried both suggestions, neither do anything. FYI, this is on Mac OS. Here's a screenshot of the clipboard's contents:

And here is a screenshot of the clipboard when it's working properly, generated with:

QApplication::clipboard()->setImage(QImage::fromData(generateByteArray()));

[kshegunov]

Something is still unclear to me ... are you trying to reduce the data size in the clipboard, or in your application. And after setting the mime to application/octet-stream have you deserialized the data from the receiving end? And how this relates to TIFF images, which are generally quite larger than pngs?

[btse]

@kshegunov said in How to control the quality/filesize of images copied to the clipboard?:

Something is still unclear to me ... are you trying to reduce the data size in the clipboard, or in your application. And after setting the mime to application/octet-stream have you deserialized the data from the receiving end? And how this relates to TIFF images, which are generally quite larger than pngs?

I am trying to reduce the size of the image in the clipboard. How can I deserialize it? I'm trying to use the contents of the clipboard in other applications, not my own. Example: Copy my image to the clipboard and then paste into a Powerpoint slide. My goal is to reduce the file size of the pasted image.

The screenshot I showed of it working properly is what happens when I copy to the clipboard as a QImage (see the code snippet). I guess internally it's converting it to a TIFF image.

[kshegunov]

I understand now. Well unfortunately nothing else comes to mind. Does it work if you do nothing about the image and just put it into the clipboard (the ordinary way)?

[btse]

@kshegunov said in How to control the quality/filesize of images copied to the clipboard?:

Does it work if you do nothing about the image and just put it into the clipboard (the ordinary way)?

Yes that works perfectly fine. But my goal is to reduce the size of the image. A 1289 × 440 image copied to the clipboard has a size of 1.7MB when pasted, which is just way too big. It's making the size of our PowerPoints huge.

[SGaist]

Then you should also resize your image to be smaller, change the encoding etc.

[btse]

@SGaist said in How to control the quality/filesize of images copied to the clipboard?:

Then you should also resize your image to be smaller, change the encoding etc.

But does quality == image resolution? I guess I could just lower the image resolution, but I'd prefer not to if there's another solution.

By encoding do you mean PNG, JPG, etc? How can I control that at the QImage/QPixMap level? They have no concept of encoding until saved to a QIODevice.

[SGaist]

You can't, QImage is an uncompressed hardware independent representation of the image that allows direct access to pixel data while QPixmap is an off-screen image representation that you can be used as a paint device so it's hardware dependent.

If you want small images in your PowerPoint document you have to start with the original image and make them lighter.

[btse]

@SGaist said in How to control the quality/filesize of images copied to the clipboard?:

If you want small images in your PowerPoint document you have to start with the original image and make them lighter.

Yes, but the question has been, how do I make the original image lighter and reflect this when copied to the clipboard?

[raven-worx]

@btse
and what about the way i already suggested?!

    QPixmap pixmap;
    QByteArray bytes;
    QBuffer buffer(&bytes);
    buffer.open(QIODevice::WriteOnly);
    pixmap.save(&buffer, "PNG", 0); // This is where you'd play with the quality parameter
    buffer.close();

    QMimeData *mimeData = new QMimeData;
         mimeData->setData("image/png", bytes);
    QApplication::clipboard()->setMimeData(mimeData);

This should definitely work, even when the your used clipboard inspector doesn't display it correctly.

[btse]

@raven-worx said in How to control the quality/filesize of images copied to the clipboard?:

@btse
and what about the way i already suggested?!

    QPixmap pixmap;
    QByteArray bytes;
    QBuffer buffer(&bytes);
    buffer.open(QIODevice::WriteOnly);
    pixmap.save(&buffer, "PNG", 0); // This is where you'd play with the quality parameter
    buffer.close();

    QMimeData *mimeData = new QMimeData;
         mimeData->setData("image/png", bytes);
    QApplication::clipboard()->setMimeData(mimeData);

This should definitely work, even when the your used clipboard inspector doesn't display it correctly.

It simply doesn't work, not sure what else to tell you. I tried pasting it to many different applications, none of them recognize the clipboard's contents. Have you been able to get this example to work? I've been testing on Mac OS 10.11.6 with Qt 4.8.7.2.

[Basilio]

Two years too late, but as I was having the exact same issue it might help a lost soul in the future.

A workaround for this is to save a temporary image and copy to clipboard the url to the file. This is recognized in most software on Mac (PPTX, Keynote included) and should work on Windows.

void ToClipboard(const QPixmap& pixmap)
{
    QString filename = "/tmp/screenshot.png";
    pixmap.save(filename);
    QList<QUrl> urls;
    urls << QUrl(filename);
    QMimeData* outputMime = new QMimeData;
    outputMime->setUrls(urls);
    qApp->clipboard()->setMimeData(outputMime);
}

Take care of the typical caveats when writing to disk from an application, but for most applications that might need this (user-generated, user-controlled operations) this is an ok workaround.