From kde-kimageshop Tue Oct 14 16:16:38 2003 From: Boudewijn Rempt Date: Tue, 14 Oct 2003 16:16:38 +0000 To: kde-kimageshop Subject: Powerpc X-MARC-Message: https://marc.info/?l=kde-kimageshop&m=106614828806481 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============0961221888==" --===============0961221888== Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_rFCj/8/PFUXqr9Q"; charset="us-ascii" Content-Transfer-Encoding: 7bit --Boundary-02=_rFCj/8/PFUXqr9Q Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline I finally finished compiling Krita on my trusty powerbook (took two whole d= ays=20 with kdelibs and the rest of koffice), and, yes, there appears to be an=20 endianness issue with Krita; all test images are shown blueish. (It's not a= =20 kimgio problem, since using the qimage->qpixmap conversion of Qt shows the= =20 same problem, even if it is a lot slower.) What would be the best way of handling this? Keeping the internal buffer in= =20 platform represenation and making load/save/import/export convert? Or conve= rt=20 just before painting the image? =2D-=20 Boudewijn Rempt | http://www.valdyas.org/index2.html --Boundary-02=_rFCj/8/PFUXqr9Q Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQA/jCFrdaCcgCmN5d8RArySAKCBfH4G6F7DsLtnQu/3ZsDv8dKGcACeI/nJ JqMbbS7KxqW7OJd5xF+d5XQ= =DfES -----END PGP SIGNATURE----- --Boundary-02=_rFCj/8/PFUXqr9Q-- --===============0961221888== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kimageshop mailing list kimageshop@mail.kde.org http://mail.kde.org/mailman/listinfo/kimageshop --===============0961221888==--