aboutsummaryrefslogtreecommitdiffstats
path: root/src/qml/qml/qqmltype_p.h
diff options
context:
space:
mode:
authorShawn Rutledge <shawn.rutledge@qt.io>2019-09-02 22:28:43 +0200
committerShawn Rutledge <shawn.rutledge@qt.io>2019-09-03 17:33:32 +0200
commite81ff5732f7884c5c1d9efb1f63ac7ad0dabbcb5 (patch)
treed62afc29c40181e9818f760142bcf31fd6368431 /src/qml/qml/qqmltype_p.h
parent45b1a3f97953fac65c6aef8e46abad865a0d0bc3 (diff)
PathMultiline: handle directly-bound QVector<QPolygonF>
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<QPolygonF> paths ...) and binding that paths property to PathMultiline.paths. In that case it appears in QQuickPathMultiline::setPaths() as a QVariant<QJSValue>, canConvert<QVector<QPolygonF>>() returns false, then canConvert<QVariantList>() 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 <paolo.angelelli@qt.io>
Diffstat (limited to 'src/qml/qml/qqmltype_p.h')
0 files changed, 0 insertions, 0 deletions