Ulf,
I reported the bug here: https://bugreports.qt.io/browse/QTBUG-77529
I will try to propose a fix which has no side effect on Qt3D.
Best regards,
Unai
Le mer. 14 août 2019 à 11:25, Ulf Hermann a écrit :
> Hello,
>
> > If I create a class with a QQmlListProperty and then initialise it
Hi Giuseppe,
When you say the QML APIs for Qt3D depend on this behaviour, you are
talking about appending to the default property right? Or are the APIs
depending in the fact that every QQmlListProperty has its contents
concatenated (I can't recall an example where this could be used)?
Best
Il 14/08/19 11:23, Ulf Hermann ha scritto:
In the following example, I would expect the list to contain 2 elements
instead of 5. What are your thoughts? Should I fill a bug report and try
to provide a fix?
Yes, that would be nice. Keep in mind that the default property should
still behave the
Hello,
> If I create a class with a QQmlListProperty and then initialise it with
> an array in some QML file, then subclass the QML type in a second QML
> file and try to override the array there, when creating an instance of
> the child class, the list contains the arrays concatenated instead
Hello,
I'm using QML for some years now but recently I have found a behaviour
which may be a bug or at least makes list property initialisation
inconsistent with the way other types are handled.
The behaviour can be traced back to (at least) Qt 5.2 and is still present
in Qt 5.13.
If I create a
