Hi everyone!
I am happy to announce that Qt 3D Studio 2.3 was released today.
Read more information from the blog post:
https://blog.qt.io/blog/2019/04/01/qt-3d-studio-2-3-released/
Big thanks to everyone involved!
br,
Jukka Jokiniva
Release Manager
The Qt Company
> By the way, conversions through QVariant are *exactly* what I implemented
in
> the examples/corelib/serialization/convert tool.
Right, I've seen these to be helpful.
The global task would allow to code like this.
~
struct MyStruct
{
int property1;
QString property2;
};
class MyObject
On Monday, 1 April 2019 12:41:59 CEST Vasily Pupkin wrote:
> The API would be QByteArray serialize(const QVariant& value), and QVariant
> might be a gadget or a collection of any depth. The only thing it does, is
> peaking inside QVariant and recursively (de)serializes properties or items.
By the
On Monday, 1 April 2019 12:41:59 CEST Vasily Pupkin wrote:
> > is too fragile and not compatible enough with standards. I recommend you
> > reconsider and think about a more standard format.
>
> Just wanted to clarify, that I am working on a solution, which is totaly
> different from datastream
01.04.2019, 13:43, "Vasily Pupkin" :
> Thanks for the answers.
>
>> I'm not sure I want to see more Datastream-based serialisation. The code
>> there
>> is too fragile and not compatible enough with standards. I recommend you
>> reconsider and think about a more standard format.
>
> Just wanted
> You can be sure that the conversion from QList to
QSequentialIterable
> will be successful, but the other way around is not given.
QSequentialIterable
> can contain QVariants of different types. I'm curious what is the use
case for
> the feature?
Imagine one could call a Q_INVOKABLE or a slot
Thanks for the answers.
> I'm not sure I want to see more Datastream-based serialisation. The code
there
> is too fragile and not compatible enough with standards. I recommend you
> reconsider and think about a more standard format.
Just wanted to clarify, that I am working on a solution, which
On Monday, April 1, 2019 11:09:27 AM CEST Vasily Pupkin wrote:
> Hi.
>
> I would like to submit a patch. Since it is probably going to break binary
> compatibility and is mostly about coding conventions, I would like to have
> some feedback before investing time.
Great!
> The general idea is to
On Monday, 1 April 2019 11:09:27 CEST Vasily Pupkin wrote:
> Hi.
>
> I would like to submit a patch. Since it is probably going to break binary
> compatibility and is mostly about coding conventions, I would like to have
> some feedback before investing time.
If it's going to break BC, it's a
Hi all,
Final downmerge from '5.12' ->'5.12.3' is now done and from now on '5.12' is
for Qt 5.12.4 release. So all changes targeted to Qt 5.12.3 release must be
done in '5.12.3' now.
We will create initial changes files as soon as possible for maintainers.
Please finalize those immediately
Hi.
I would like to submit a patch. Since it is probably going to break binary
compatibility and is mostly about coding conventions, I would like to have
some feedback before investing time.
The general idea is to create a playground project for automatic
(de)serialization for Qt (not manual,
11 matches
Mail list logo
