2015-05-19 22:12 GMT+04:00 Rutledge Shawn :
> I think the new API should have multi-page support. It would be useful
> for pdf, djvu, multi-page tiff, and for looking at individual frames of
> animated gif, png, etc., to the extent that we write plugins for those.
>
IIUC, this already covered by
Thanks for reply.
Yes, frames should actually be renamed to something more generic (array
element? page? resourceCount? - i couldn’t find the right name yet). Actually,
DDS doesn’t support animation, but it supports texture arrays which should be
implemented using "frames".
I didn’t think abou
I think the new API should have multi-page support. It would be useful for
pdf, djvu, multi-page tiff, and for looking at individual frames of animated
gif, png, etc., to the extent that we write plugins for those.
I wrote a QQuickImageProvider for PDF (using poppler), but requestImage takes
o
Hello everybody!
Recently i’ve started a project of a new imageformats API. The reasoning is
that there are a lot of limitations in the current API: no way to save file
containing an array of images, bad error handling, no support for the EXIF.
Implementing those features requires ABI breakage
