qt/qtdeclarative.git, branch v5.9.3 Qt Declarative (Quick 2) Fix crash when accessing pixmap on default QSGSoftwareInternalImageNode 2017-11-17T18:15:09+00:00 Allan Sandfeld Jensen allan.jensen@qt.io 2017-11-16T16:41:44+00:00 08778586413adad7b3af35c7cb97416757d599c0 Task-number: QTBUG-64562 Change-Id: I52e07b0d8b7a5d1cc960431dcbd1a90dd3e7e518 Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io> Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io> 
Task-number: QTBUG-64562
Change-Id: I52e07b0d8b7a5d1cc960431dcbd1a90dd3e7e518
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>
Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io>
Fix crash with dangling context object pointers 2017-11-14T08:23:57+00:00 Andy Shaw andy.shaw@qt.io 2017-11-13T12:56:09+00:00 d188cdd7378e0e8b384fa812b5907638075d1206 This is a regression introduced by commit e22b624d9ab1f36021adb9cdbfa9b37054282bb8, where the object that owns the QML context would destroy the context upon destruction. Now the context may live longer and thus the context->contextObject pointer would become a dangling pointer. Task-number: QTBUG-64166 Change-Id: I1df631fa11187abdeff735d8891ad7907e8d4a3d Reviewed-by: Lars Knoll <lars.knoll@qt.io> 
This is a regression introduced by commit
e22b624d9ab1f36021adb9cdbfa9b37054282bb8, where the object that owns the
QML context would destroy the context upon destruction. Now the context
may live longer and thus the context->contextObject pointer would become
a dangling pointer.

Task-number: QTBUG-64166
Change-Id: I1df631fa11187abdeff735d8891ad7907e8d4a3d
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
Blacklist tst_qquickwidget::enterLeave() on Mac 2017-11-14T08:23:52+00:00 J-P Nurmi jpnurmi@qt.io 2017-11-09T12:01:08+00:00 19f02c691f790e2b38a23a3955590383425784e7 Task-number: QTBUG-64397 (cherry picked from commit 5f16aa795d39969d93b520861a1e86729c7db90e) Change-Id: I28268ea87b81dd1f7dbf8bb5a8eb421962cc5f31 Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io> 
Task-number: QTBUG-64397
(cherry picked from commit 5f16aa795d39969d93b520861a1e86729c7db90e)
Change-Id: I28268ea87b81dd1f7dbf8bb5a8eb421962cc5f31
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
Add changes file for Qt 5.9.3 2017-11-12T08:16:45+00:00 Jani Heikkinen jani.heikkinen@qt.io 2017-11-02T06:52:59+00:00 706ea1f63ede8e84e4ccc70baa0c93b493c1badf Task-number: QTBUG-64181 Change-Id: I85a6150e00143b379143c353a37e844cb9708627 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> Reviewed-by: Simon Hausmann <simon.hausmann@qt.io> 
Task-number: QTBUG-64181
Change-Id: I85a6150e00143b379143c353a37e844cb9708627
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
Improve encapsulation of the the IR de-serialization from QtQuick Compiler 2017-11-12T08:16:36+00:00 Simon Hausmann simon.hausmann@qt.io 2017-11-09T09:43:42+00:00 fdfb34c84ba01114d34259cd88a2b84fa22eb610 The code used by QQC to deserialize the IR requires setting the javaScriptCompilationUnit member in order to connect the generated C++ code. Knowledge of the QmlIR::Document data structure layout on the side of the generated code (thus application) has its downsides though (see referenced bug). We can avoid that dependency easily by doing the entire de-serialization on the QtQml library side. The old "API" (load member function) is still around until the qqc change is also in. Task-number: QTBUG-63474 Change-Id: I239838afacc71474c86114b5b05679ff36e4c2e2 Reviewed-by: Lars Knoll <lars.knoll@qt.io> 
The code used by QQC to deserialize the IR requires setting the
javaScriptCompilationUnit member in order to connect the generated C++
code. Knowledge of the QmlIR::Document data structure layout on the side
of the generated code (thus application) has its downsides though (see
referenced bug). We can avoid that dependency easily by doing the entire
de-serialization on the QtQml library side.

The old "API" (load member function) is still around until the qqc
change is also in.

Task-number: QTBUG-63474
Change-Id: I239838afacc71474c86114b5b05679ff36e4c2e2
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
Fix ListView::positionViewAtIndex with ListView.Contain mode 2017-11-07T12:21:11+00:00 Joni Poikelin joni.poikelin@qt.io 2017-10-23T10:51:43+00:00 54f15f5df5cf545bf4d675ccbafecd482b4a2b0b Sticky headers and footers weren't accounted for when calculating new view position causing the requested item to be left behind them. Task-number: QTBUG-63974 Change-Id: Id69579643a942e8558960b2c8b0fee980fa86947 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> 
Sticky headers and footers weren't accounted for when calculating new
view position causing the requested item to be left behind them.

Task-number: QTBUG-63974
Change-Id: Id69579643a942e8558960b2c8b0fee980fa86947
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
QQuickWindow: cleanup pointer event instances 2017-11-07T12:20:58+00:00 J-P Nurmi jpnurmi@qt.io 2017-07-14T14:37:22+00:00 4331ccd4b735d9d721a384193a3d42ee2ce6c805 Pointer event instances are QObject-children of QQuickWindow, meaning that they remain alive after ~QQuickWindow(), until execution reaches ~QObject(). Make sure the pointer event instances are cleaned up in ~QQuickWindow() to avoid accessing them later during the destruction phase. Task-number: QTBUG-61434 Change-Id: Icd4576e7581524773a3eb33864fdd64df821e0e8 Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io> Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> 
Pointer event instances are QObject-children of QQuickWindow, meaning
that they remain alive after ~QQuickWindow(), until execution reaches
~QObject(). Make sure the pointer event instances are cleaned up in
~QQuickWindow() to avoid accessing them later during the destruction
phase.

Task-number: QTBUG-61434
Change-Id: Icd4576e7581524773a3eb33864fdd64df821e0e8
Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Never create pointer events from mouseGrabberItem() 2017-11-07T05:03:01+00:00 Jan Arve Saether jan-arve.saether@qt.io 2017-11-06T13:20:59+00:00 75cc5fdc219c42ae26ec8497647eda5440c324f2 Normally, this was not a problem, but it is problematic during QQuickWindow destruction: The list of pointer event instances are destroyed, but later the grabber is removed (through call to removeGrabber()). This queries the mouseGrabberItem(), which would create a new pointer event instance. It also has the benefit that d->pointerEventInstances are now only populated due to actual incoming events. Task-number: QTBUG-61434 Change-Id: I4e7b6f5643f3b971138a1f7c7237ee734d29783c Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> 
Normally, this was not a problem, but it is problematic during
QQuickWindow destruction:
The list of pointer event instances are destroyed, but later the grabber
is removed (through call to removeGrabber()).  This queries the
mouseGrabberItem(), which would create a new pointer event instance.

It also has the benefit that d->pointerEventInstances are now only
populated due to actual incoming events.

Task-number: QTBUG-61434
Change-Id: I4e7b6f5643f3b971138a1f7c7237ee734d29783c
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
QQuickWidget: pass enter and leave events to the offscreen window 2017-11-06T23:56:16+00:00 Andy Shaw andy.shaw@digia.com 2015-12-02T08:51:35+00:00 37d25a5112cdf13620715c03d6bdbd1bc3cde515 By passing the enter and leave events to the offscreen window it will enable mouse areas inside a QQuickWidget to know when the mouse has actually entered or left the area if it is covering the whole item. Task-number: QTBUG-45557 Change-Id: I670ebe30e367e919c73fed449bf2bed7ca42b5fd Reviewed-by: Gatis Paeglis <gatis.paeglis@qt.io> 
By passing the enter and leave events to the offscreen window it will
enable mouse areas inside a QQuickWidget to know when the mouse has
actually entered or left the area if it is covering the whole item.

Task-number: QTBUG-45557
Change-Id: I670ebe30e367e919c73fed449bf2bed7ca42b5fd
Reviewed-by: Gatis Paeglis <gatis.paeglis@qt.io>
Fix coverity reported warning 2017-11-06T11:25:45+00:00 Lars Knoll lars.knoll@qt.io 2017-11-06T07:22:03+00:00 5fc892ef86870021ad11d0be6981aa9630c1c01c The variable wasn't initialized in any constructor. This didn't cause issues in practice, as it always got set in optimizeRenderList(). Change-Id: I37459bb2d51bbe2bb881aaefffd6972a5345c75d Reviewed-by: Andy Nichols <andy.nichols@qt.io> 
The variable wasn't initialized in any constructor. This
didn't cause issues in practice, as it always got set in
optimizeRenderList().

Change-Id: I37459bb2d51bbe2bb881aaefffd6972a5345c75d
Reviewed-by: Andy Nichols <andy.nichols@qt.io>