> Sent: Wednesday, May 16, 2018 at 11:52 PM
> From: "Thiago Macieira"
> To: interest@qt-project.org
> Subject: Re: [Interest] QDatastream, QMap, QImage serialization
>
> On Wednesday, 16 May 2018 14:38:08 PDT Jérôme Godbout wrote:
> > You will need to provide your own
> >
> > QDataStream& operato
On Wednesday, 16 May 2018 14:38:08 PDT Jérôme Godbout wrote:
> You will need to provide your own
>
> QDataStream& operator<<(QDataStream& ds, const QImage& img)
That's not needed (and won't compile). It already exists.
The problem is that QVariant doesn't know how to call it. So when you have a
You will need to provide your own
QDataStream& operator<<(QDataStream& ds, const QImage& img)
{
ds << img.height() << img.width() << img.format() << img.data()
}
and
QDataStream& operator>>(QDataStream& ds, QImage& img)
{
int height;
ds >> height;
img.setHeight(height);
...
}
On Wednesday, 16 May 2018 13:51:39 PDT Jason H wrote:
> I'm trying to write a GUI utility to provide a simple UI. I'm wanting a
> no-frills database of several Qt types, and I'm trying to use QVariantMap
> for that. It's going well except that QImages aren't being serialized
> correctly. Yes, I kno
I'm trying to write a GUI utility to provide a simple UI. I'm wanting a
no-frills database of several Qt types, and I'm trying to use QVariantMap for
that. It's going well except that QImages aren't being serialized correctly.
Yes, I know there is a QVariant limitation with "GUI types" (
http:/
Hi,
This is a very positive and long anticipated development.
Excellent!
Kind regards,
Robert
On Wed, May 16, 2018 at 12:20 PM, Tuukka Turunen wrote:
>
>
> Hi,
>
>
>
> Contribution of source code is now allowed via Qt systems such as bug
> reports and forums. Traditionally all source code cont
On 05/16/2018 06:04 AM, Thiago Macieira wrote:
Ok, so not the standard C library. But it is still the case for POSIX and
Win32.
In fact, the man page for write(2) says specifically
[...] It is not an error if this number is smaller
than the number of bytes requested; this may
Am Wed, 16 May 2018 10:49:06 +
schrieb "Trillmann, Jens" :
> every other file in the platformplugin is LGPL licensed. From my
> understanding I would violate the LGPL license if I would try to
> distribute the app in this form, because a user could not easily swap
> the provided Qt-library
> From my understanding I would violate the LGPL license if I would try to
distribute the app in this form, because a user could not easily swap
the provided Qt-library with his own. The app itself is under the
non-compatible EUPL.
You can ship your app's .o files to allow other people to relink
Hi,
I'm currently trying to link our app on iOS dynamically against Qt. From
the technical standpoint everything seems to be working, but I have a
problem with the licensing.
I would like to conform to the LGPL license, meaning that I want to link
against all Qt parts dynamically, but I have t
Hi,
Contribution of source code is now allowed via Qt systems such as bug reports
and forums. Traditionally all source code contributions to the Qt Project are
governed via Contribution License Agreement (CLA), except possibility given to
the commercial license holders to provide bug fixes and
11 matches
Mail list logo
