qt/qtdeclarative.git/src/quick/util/qquickpath.cpp, branch 5.15.17

Merge remote-tracking branch 'origin/tqtc/lts-5.15.5' into tqtc/lts-5.15-opensource

2022-05-16T15:16:38+00:00

Change-Id: I5e0eef69a31bcfda65cf965fb4c8c330581e5168

Doc: Fix the Shapes table to reflect reality

2021-05-12T10:35:05+00:00

PathPolyline and PathMultiline do not have GL_NV_path_rendering
support so this is updated to reflect that.

Change-Id: Iaa119e51bb22d6c8b4907818ffda96cca299893d
Reviewed-by: Laszlo Agocs

Revert "Update commercial license headers"

2021-03-24T14:55:37+00:00

This reverts commit 7b1331c789df0ac12d7cf5aa5f8967b8651a4cfa.

Revert of commercial license headers is required for Qt 5.15.3
opensource release.

Task-number: QTBUG-91108
Change-Id: I47eb004523bdb3beb16e9fd51e40da6f738f9f34
Reviewed-by: Jukka Jokiniva

Update commercial license headers

2021-02-02T14:34:24+00:00

Updated header.COMM to the files in tqtc-qtdeclarative.
Examples, documentation files or tests are not updated.

The commercial license header may contain some
additional lines so that its line count equals with
the earlier license header. Reason for this is that
some autotests use hard coded line numbers and a
change in the line count causes failures in tests.

Task-number: QTQAINFRA-4161
Change-Id: Ic1d011aa01b1fe7242bcbbf72d5ab454d1015cf9
Reviewed-by: Ulf Hermann

Fix vertical position of PathText

2020-01-29T13:45:41+00:00

The PathText would always translate to y=0, regardless of what y
was set to. We should obviously get the y coordinate of the shape
*before* translating it into position to find the distance from
the baseline.

This change also updates the example, which had not been updated
to the changed origin of the PathText, and it adds a Lancelot test
for keeping track of the PathText shape rendering.

Change-Id: I940ac956af5229842739f8d8751a1f13bb86b8e7
Reviewed-by: Eirik Aavitsland

Introduce PathText path element

2020-01-21T10:48:54+00:00

For text rendering in Qt Quick, we currently have the limitation
that when rendering text at such a large size that the distance
fields start showing artifacts, the only option is to use
NativeRendering, which will look nice, but which will use a lot
of texture memory for the glyph cache, since it will actually
cache the glyphs at the requested size.

A suggested approach would be to fall back to using triangulated
paths when the font gets large enough, but the work on this was
never completed.

It turns out that we can get this now, basically for free, since
we already support rendering arbitrary QPainterPaths using
Qt Quick Shapes. The only thing missing is the ability to add
the path of a given text to the shape. This patch fills in that
gap.

Note that this is currently not supported by nvidia renderer.

[ChangeLog][QtQuick] Added PathText path element which can be
used together with Qt Quick Shapes to get text rendering that
does not cache glyphs in a texture, but triangulates the
outlines of the glyphs instead.

Change-Id: I436e1476b129b324cf7a54f89a1b18e0579e8185
Reviewed-by: Laszlo Agocs

Replace QVariant::type with QVariant::userType

2020-01-17T10:31:35+00:00

as type is going to be deprecated.

This change was done automatically with the help of clazy.
In addition, ColumnRoleMetadata was changed to take an int instead
of a QVariant::Type

Change-Id: Ibc02d7b52e7d931a56c19fdebc4788b5e6df2a39
Reviewed-by: Lars Knoll

Doc: Fix documentation warnings

2019-11-11T09:53:52+00:00

There were a lot of documentation warnings introduced by the
separation of QtQml.Models and QtQml.WorkerScript modules
from the QtQml documentation project into their own
sub-projects.

Fix the above, and also ensure that the experimental
Qt.labs.qmlmodels QML types are listed in the documentation,
and add them also on the QML module page for QtQml.Models.

A few warnings remain, they may be indicative of issues
not in the scope of this commit.

Fixes: QTBUG-79812
Change-Id: Idc25c976e4c96feab4aae893519d6c9245f57a64
Reviewed-by: Paul Wicking

PathMultiline: handle directly-bound QVector

2019-09-03T15:33:32+00:00

The autotest in 811b15bd161d12e5c85e093f9f492a0c4fa278d6 only tested
what happens if the vector of polygons is passed via a QVariant to the
PathMultiline paths property.  But the intention (as documented) was to
literally support an object with Q_PROPERTY(QVector paths ...)
and binding that paths property to PathMultiline.paths.  In that case
it appears in QQuickPathMultiline::setPaths() as a QVariant,
canConvert>() returns false, then
canConvert() returns true.  Nevertheless each variant
in the QVariantList is a QPolygonF, as expected.  So we need another
check to detect this case.  Also added a test specifically for that.

Fixes: QTBUG-77929
Change-Id: I84d0a45326d5f007b8ba3cc9bb1fbccf0345d812
Reviewed-by: Paolo Angelelli

PathMultiline: allow lists/vectors of polygons or point lists/vectors

2019-09-02T20:23:03+00:00

If a C++ model object can make a vector of vectors of points available
directly, and it is bound to a PathMultiline's paths property to provide
the view layer, it's a waste of time to convert it to a QVariantList of
QVariantLists and back again.  Changing the type of the property to
QVariant instead of QVariantList enables an extensible set of supported
types: all those that make sense.

Fixes: QTBUG-77929
Change-Id: If749c2171173e7b9933fc9ecdf6d2741dc1c7500
Reviewed-by: Paolo Angelelli