Change-Id: Ic367e6b9da1c5e1508f1bc4aaeceea5f9f49dab8
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>

Extend the plugin documentation to explicitly mention that the
socket:// scheme supports only unencrypted connection.

Fixes: QTBUG-146191
Pick-to: 6.11 6.8
Change-Id: I1dbc3d24a4d1e66ee49109bfb5505b2508900469
Reviewed-by: Juha Vuolle <juha.vuolle@qt.io>

Amends e568470c6409febdb5187e3f53af32164c63169f which included this
header but never used it.

Pick-to: 6.11 6.8
Change-Id: If1cd4a26d801276cbe18b9b0d0b4485cad17b074
Reviewed-by: Marc Mutz <marc.mutz@qt.io>
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
Reviewed-by: Juha Vuolle <juha.vuolle@qt.io>

This virtual function was only overloaded by the Eager versions of the
Private subclasses, where it was implemented as Q_UNREACHABLE() to
make sure that it is never called.

This shows that we can get rid of this virtual function and inline its
base implementation into its only caller - ensureBoundingBoxUpdated().

Task-number: QTBUG-144952
Pick-to: 6.11 6.8
Change-Id: I9b40d6321892702e6aedb3ef533b761c926480cd
Reviewed-by: Marc Mutz <marc.mutz@qt.io>
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>

These classes use lazy evaluation of the bounding box and clipper path.
Since these classes use implicit sharing, that could cause data races,
if the getter was called on objects in different threads that share the
same internal Private.

Fix data races by making sure that in the const getters we do the
evaluation of the cached data under a mutex. Note that non-const method
calls on an object with a shared Private are safe, as they detach before
modifying the data. Additionally, reads are confined to input variables,
which also lazy evaluation only reads, so there are no conflicts that
could lead to data races.

Also, make the cached members mutable and the relevant helper functions
const, which allows to drop const_cast<> from the calling side.
Note that this const_cast was never an UB, because it was only done
on a Private, which was never declared as const.

We now need to introduce custom copy-constructors for Private classes,
because we need to make sure that we only copy non-cached members and
do not access other's mutex-proteced fields.

Fixes: QTBUG-144952
Pick-to: 6.11 6.8
Change-Id: I7f7e9abea83e9b9c9e9254e9fab5132623931a55
Reviewed-by: Marc Mutz <marc.mutz@qt.io>

It was previously a member variable in the parent QGeoPathPrivateBase
class. However, it is not used in QGeoPath after the refactoring of the
algorithm in QGeoPathPrivate::lineContains(), that was done in
accbd54f5d6385b986a560f533296a9d0257fbf5.

As a result, the only user is QGeoPolygonPrivate, so move it there.
In that class, the only users are updateClipperPath() and
polygonContains() (which also calls updateClipperPath() before using
the cached values). As a result, compute the m_leftBoundWrapper value
only in updateClipperPath() and remove all the other updates, as they
are redundant.

Task-number: QTBUG-144952
Pick-to: 6.11 6.10 6.8
Change-Id: I9ba983bcab9c8e5e0e3f673cc11050e95fa4d937
Reviewed-by: Marc Mutz <marc.mutz@qt.io>
Reviewed-by: Juha Vuolle <juha.vuolle@qt.io>

Point potential contributors to contribute.qt-project.org.

Change-Id: Icd4bc4b77acbabb3b47e6093c4564fa05ce3014f
Reviewed-by: Paul Wicking <paul.wicking@qt.io>

Change-Id: I463985eb017bb9c8e94ac00671696ef50b184b5e
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>

Change-Id: I6a63c220f93887de3317ce7e7497edab66514106
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>

Change-Id: I00976d5e0078488a4a358f47b659952350e9ebf5
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>