If installOn was called on an object with an alias to a BINDABLE
property (e.g. via PropertyChanges), we would fail to resolve the
UntypedBindable. The reason is that we were attempting a direct call of
the static meta-objects function (via qt_metacall). This certainly
bypasses interceptors, but it also bypasses the QQmlVMEMetaObject logic
which resolves aliases.

After resolution, we now always use QMetaObject::metacall, but set a
flag on any potential interceptor meta-object. We need to set that flag
recursively on the meta-object parent chain, as we can't know where
the relevant interceptor sits in the parent chain.
We have to resolve any aliases first, as we'd otherwise set the flag on
the wrong dynamic meta-object if the alias points to another object.

Alternatively, we could modify the metacall for BINDABLE to also pass an
(optional) flags argument, but that change requires larger coordination
between qtbase and declarative, and should at least not be backported.

Fixes: QTBUG-148815
Pick-to: 6.12 6.11 6.8
Change-Id: I75836c8402c1c9df4e28c61e0199c5e1d359b8b6
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>

First, we can use the static metacall mechanism of QQmlPropertyData for
this. Second, we cannot rely on ensurePropertyCache(). It might still
return a nullptr if we are dealing with a dynamic metaobject, resulting
in a crash.

Pick-to: 6.9 6.8 6.5
Change-Id: I0497c23f9fa6d68857e6329746193e90ee7ecfc6
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

Change-Id: I95474784c1eb8c8d8f5dafd33dcc32f532bffe47
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Sami Shalayel <sami.shalayel@qt.io>
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Liang Qi <liang.qi@qt.io>
Reviewed-by: Andy Nichols <andy.nichols@qt.io>
Reviewed-by: Matthias Rauter <matthias.rauter@qt.io>
Reviewed-by: Jøger Hansegård <joger.hansegard@qt.io>

According to QUIP-18 [1], all test files should be
LicenseRef-Qt-Commercial OR GPL-3.0-only

[1]: https://contribute.qt-project.org/quips/18

Pick-to: 6.7
Task-number: QTBUG-121787
Change-Id: I26d72e8de04d4c7c57b3b7838af5d033265de5ba
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Reviewed-by: Kai Köhne <kai.koehne@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>

Replace the current license disclaimer in files by
a SPDX-License-Identifier.
Files that have to be modified by hand are modified.
License files are organized under LICENSES directory.

Pick-to: 6.4
Task-number: QTBUG-67283
Change-Id: I63563bbeb6f60f89d2c99660400dca7fab78a294
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>

Previously each test would include and build sources from the shared
folder. Now we make those sources a library, build it once, then have
each test link to it instead.

We also take the opportunity to move some helpers that qtquickcontrols2
had added into the quicktestutils library where it makes sense, and
for the helpers that don't make sense to be there, move them into
quickcontrolstestutils.

We add the libraries to src/ so that they are internal modules built as
part of Qt, rather than tests. That way we can use them in a standalone
test outside of qtdeclarative.

Task-number: QTBUG-95621
Pick-to: 6.2
Change-Id: I0a2ab3976fdbff2e4414df7bdc0808f16453b80a
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

In contrast to other QPropertyBindings, QQmlPropertyBinding could be
executed even if it is not installed on a property. This would happen if
we keep a strong reference to it, remove it from a property, and change
one of the observed JS dependencies. That would lead to a call of
expressionChanged, and then subsequently to an evaluate call. As setting
and removing the binding from a property can be done purely in C++, we
cannot detect this in the engine (which would allow us to disable the
binding, so that expressionChanged does not get called). Thus, we simply
check if the property data pointer is set when expressionChanged is
called, and return otherwise.

Task-number: QTBUG-89505
Change-Id: I933c1b3285d6472b1d2c6512ad37911090861298
Reviewed-by: Maximilian Goldstein <max.goldstein@qt.io>
Reviewed-by: Andrei Golubev <andrei.golubev@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>

QQmlAnyBinding is meant to abstract over the differences between
classical, QQmlAbstractBinding derived bindings and the newer
QPropertyBindingPrivate based ones. It can be used to store, receive,
remove, create and set bindings of both types.

In addition, this patches adds the functionality to create a
QQmlPropertyBinding from a code string, which was so far only
possible with QQmlBinding; and adds a few methods to QBiPointer to ease
the implementation of QQmlAnyBinding.

Task-number: QTBUG-91000
Change-Id: I7076d6fb426f315f32c1b054c5c3ba56312bed29
Reviewed-by: Andrei Golubev <andrei.golubev@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>