qt/qtdeclarative.git, branch v5.12.4 Qt Declarative (Quick 2) Add changes file for Qt 5.12.4 2019-05-28T12:19:15+00:00 Antti Kokko antti.kokko@qt.io 2019-05-23T12:20:44+00:00 48b4df598c88782f031f3df62964e159feeb20fb Change-Id: I6980ffaed4da941fbcd56af36bba7e5abf3dd878 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> 
Change-Id: I6980ffaed4da941fbcd56af36bba7e5abf3dd878
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Bump version 2019-05-23T09:16:56+00:00 Frederik Gladhorn frederik.gladhorn@qt.io 2019-05-23T09:16:56+00:00 bae6f43d8e1fafec2771bdeddffa9edaf1bf6130 Change-Id: I0810ede89313a6ee3ee31a352fda620835dfb055 
Change-Id: I0810ede89313a6ee3ee31a352fda620835dfb055
Don't add local for anonymous function's "name" 2019-05-21T16:03:47+00:00 Ulf Hermann ulf.hermann@qt.io 2019-05-21T13:10:45+00:00 3e716029ae61bf4c7bb33643ac331156e70e34f1 Instead, populate their "name" property directly from the surrounding object pattern if applicable, without adding locals. This fixes some ecmascript tests where functions were assigned to the key "eval" in an object. The JS engine then rejected that because you shouldn't use eval in strict mode. That should be close enough to test for regressions. Fixes: QTBUG-75880 Change-Id: Iacc45a3f7b0eb90cddc6ecf6d2bada616d2cf355 Reviewed-by: Lars Knoll <lars.knoll@qt.io> 
Instead, populate their "name" property directly from the surrounding
object pattern if applicable, without adding locals. This fixes some
ecmascript tests where functions were assigned to the key "eval" in an
object. The JS engine then rejected that because you shouldn't use eval
in strict mode. That should be close enough to test for regressions.

Fixes: QTBUG-75880
Change-Id: Iacc45a3f7b0eb90cddc6ecf6d2bada616d2cf355
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
Doc - minor cleanup 2019-05-21T14:56:14+00:00 Kavindra Palaraja kpalaraja@luxoft.com 2019-05-21T14:05:08+00:00 9e919489c4e6b0c110281fda139fff84c1c71995 * Small fixes to improve readability * Fixed some typos * Updated the link to an old-ish MSDN article * Used a list instead of a long paragraph in the introduction area * Swapped a long list for a table for environment variables Change-Id: Id7eeee5c5b24f96e4577212a385cfa766e809d1f Reviewed-by: Simon Hausmann <simon.hausmann@qt.io> 
* Small fixes to improve readability
* Fixed some typos
* Updated the link to an old-ish MSDN article
* Used a list instead of a long paragraph in the introduction area
* Swapped a long list for a table for environment variables

Change-Id: Id7eeee5c5b24f96e4577212a385cfa766e809d1f
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
Fix lookups of properties in QML singletons 2019-05-21T10:42:45+00:00 Simon Hausmann simon.hausmann@qt.io 2019-05-20T14:09:13+00:00 2f4479857d2b68f8cd3267b2f2b3c652ada431ed An unqualified name that points to a QML singleton will evaluate to a QQmlTypeWrapper JS object. A member lookup in such an object is not guaranteed to always produce the same property. The property cache check may protect us from that, but we must still retrieve the QObject singleton for every lookup. Task-number: QTBUG-75896 Change-Id: Ibd9bac6e5c2047f838758811790b299ace636446 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> 
An unqualified name that points to a QML singleton will evaluate to a
QQmlTypeWrapper JS object. A member lookup in such an object is not
guaranteed to always produce the same property. The property cache check
may protect us from that, but we must still retrieve the QObject
singleton for every lookup.

Task-number: QTBUG-75896
Change-Id: Ibd9bac6e5c2047f838758811790b299ace636446
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Fix leaking scene graph rendering contexts 2019-03-15T10:16:12+00:00 Simon Hausmann simon.hausmann@qt.io 2019-03-15T10:13:05+00:00 c61a75cd6a4a9cd7b3594b205fcac8fc1208d493 When using the threaded render loop, the rendering thread assumes ownership of the rendering context. If the rendering thread is never started, that context is leaked. This happens in tests sometimes when we create and destroy a window without waiting for exposure. So this patch maintains the ownership in the render loop for created contexts until the per-window thread is started. Task-number: QTBUG-74348 Change-Id: Ifa397fab0833c82110ac4571c1e3790351c43afd Reviewed-by: BogDan Vatra <bogdan@kdab.com> Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> 
When using the threaded render loop, the rendering thread assumes
ownership of the rendering context. If the rendering thread is never
started, that context is leaked. This happens in tests sometimes when we
create and destroy a window without waiting for exposure.

So this patch maintains the ownership in the render loop for created
contexts until the per-window thread is started.

Task-number: QTBUG-74348
Change-Id: Ifa397fab0833c82110ac4571c1e3790351c43afd
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Print a warning when encountering a non-relative URL in a qmldir file 2019-05-16T13:48:58+00:00 Ulf Hermann ulf.hermann@qt.io 2019-05-13T12:13:34+00:00 869b89bde8b0149a875e6e23466820f573e4a73c This is not supported because supporting it would encourage users to create components that won't work on other systems or that will confuse qmlplugindump. QML still parses and loads those components, but you should really use relative paths. Task-number: QTBUG-48809 Change-Id: I9c81671cb5c4ea59b8c884ff24ad02e82047e9d6 Reviewed-by: Simon Hausmann <simon.hausmann@qt.io> 
This is not supported because supporting it would encourage users to
create components that won't work on other systems or that will confuse
qmlplugindump. QML still parses and loads those components, but you
should really use relative paths.

Task-number: QTBUG-48809
Change-Id: I9c81671cb5c4ea59b8c884ff24ad02e82047e9d6
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
Re-add cache for looking up attached properties objects 2019-05-16T13:34:40+00:00 Ulf Hermann ulf.hermann@qt.io 2019-05-16T12:15:06+00:00 1ee7afa50fe5fe995008dee5d00638b894145d12 c018df5b4075ae962966d4df7653d476dab02840 removed an optimization in qmlAttachedPropertiesObject. The attached properties ID was implicitly cached as it was static in a method templated by the type the attached properties were registered for. We don't actually need the ID for this, as we can also cache the function pointer. Fixes: QTBUG-75609 Change-Id: I15e728ce4bbb89062a84ee6f113b1188faa32b92 Reviewed-by: Simon Hausmann <simon.hausmann@qt.io> 
c018df5b4075ae962966d4df7653d476dab02840 removed an optimization in
qmlAttachedPropertiesObject. The attached properties ID was implicitly
cached as it was static in a method templated by the type the attached
properties were registered for. We don't actually need the ID for this,
as we can also cache the function pointer.

Fixes: QTBUG-75609
Change-Id: I15e728ce4bbb89062a84ee6f113b1188faa32b92
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
Fix assert in QSGBasicInternalImageNode::updateGeometry 2019-05-16T11:10:42+00:00 Allan Sandfeld Jensen allan.jensen@qt.io 2019-05-15T11:54:31+00:00 acc3d31f7069a244c32fca01f8a2873e0798c785 Handle that hCells and vCells might be 0 with non-0 innerTarget. Fixes: QTBUG-73768 Change-Id: Id9dde2368e8cdfe40e5b287b16c0473ad7c12d69 Reviewed-by: Robin Burchell <robin.burchell@crimson.no> 
Handle that hCells and vCells might be 0 with non-0 innerTarget.

Fixes: QTBUG-73768
Change-Id: Id9dde2368e8cdfe40e5b287b16c0473ad7c12d69
Reviewed-by: Robin Burchell <robin.burchell@crimson.no>
Do not synthesize a double click event if the event point moved too far 2019-05-15T14:43:42+00:00 Jan Arve Sæther jan-arve.saether@qt.io 2019-05-14T10:13:01+00:00 56fbc277a1acc49d9ead4c89edd250a021ef2a01 We need to respect QPlatformTheme::TouchDoubleTapDistance Fixes: QTBUG-75770 Change-Id: I2adc7097bb29cb93beb2609a8a806a666856a0c8 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> 
We need to respect QPlatformTheme::TouchDoubleTapDistance

Fixes: QTBUG-75770
Change-Id: I2adc7097bb29cb93beb2609a8a806a666856a0c8
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>