- 04 Jan, 2021 2 commits
-
-
MikeSalmela authored
[qtdeclarative] Fix License in spec. Contributes to JB#50383 See merge request !35
-
Mike Salmela authored
-
- 28 Oct, 2020 1 commit
-
-
Matti Lehtimäki authored
Fix build with python3. Cleanup spec. See merge request !33
-
- 15 Oct, 2020 2 commits
-
-
Matti Lehtimäki authored
-
Matti Lehtimäki authored
-
- 02 Oct, 2020 2 commits
-
-
Matti Kosola authored
[qtdeclarative] Fix some type errors with qreal=double. Contributes to JB#49697 See merge request !34
-
pvuorela authored
-
- 20 Aug, 2020 1 commit
-
-
Andrew den Exter authored
[qtdeclarative] Remove unintentional debug statement. Contributes to JB#50336 See merge request !32
-
- 12 Aug, 2020 1 commit
-
-
Andrew den Exter authored
-
- 04 Aug, 2020 1 commit
-
-
Andrew den Exter authored
Add a QSGOpacityNode flag which allows a node to ignore inherited opacity See merge request !31
-
- 26 Jun, 2020 1 commit
-
-
Andrew den Exter authored
[qtdeclarative] Add a QSGOpacityNode flag which allows a node to ignore inherited opacity. Contributes to JB#50336
-
- 19 Mar, 2020 1 commit
-
-
Andrew den Exter authored
[qtdeclarative] Load images in an OpenGL texture friendly format. Contributes to JB#49193 See merge request !30
-
- 18 Mar, 2020 1 commit
-
-
Andrew den Exter authored
Pre-emptively convert images in the pixmap cache to RGBX8888 or RGBA8888_Premultipled to avoid potentially doing the conversion in the render thread where it will directly impact the frame rate.
-
- 07 Feb, 2020 1 commit
-
- 17 Jan, 2020 1 commit
-
-
Martin Kampas authored
Do not exclude types that are reachable through dependencies, but only become registered (exported) after the dumped module is imported. This happens e.g. when a private submodule exists as a dependency and it extends types from the public module. The extended types become reachable when the private submodule is loaded as a dependency, but only become registered (exported) after the public module is loaded.
-
- 13 Nov, 2019 1 commit
-
-
Andrew den Exter authored
[qtdeclarative] Fix crash due to an interaction between an item layer and anchors. Fixes JB#44681 See merge request !28
-
- 11 Nov, 2019 1 commit
-
-
Andrew den Exter authored
Evaluating anchors in QQuickItem::componentComplete() will change size and position bindings and the right code reacting to those changes could create a layer after QQuickItemPrivate::completeCreate is set to true which means QQuickItemLayer::classBegin() would not be called, but QQuickItemLayer::componentComplete() would be meaning QQuickItemLayer::activate() would be called twice and it would be added as an item change listener twice. If the layer was then ever deactivated it would only be removed as a listener once and changes to the parent size would update the layers size when it wasn't expecting it.
-
- 07 Nov, 2019 2 commits
-
-
Timur Kristóf authored
- 28 Oct, 2019 1 commit
-
-
Timur Kristóf authored
Previously there was no way to know what area is occupied by each line in a QML Text element. This commit adds new API to expose implicitWidth and isLast on QQuickTextLine for use in the lineLaidOut signal. It also adds improved documentation to the lineLaidOut signal and an example usage of the new API to the text layout example. An example use case of the new API is eg. to allow embedding timestamps and indicators within a text paragraph, to enable creating more efficient layouts. [ChangeLog][QtQuick][Text] Added new API that exposes implicitWidth, and isLast on the QQuickTextLine for use in the lineLaidOut signal. This allows the user to layout other items relative to the lines of text. Fixes: QTBUG-78277 Change-Id: Ibc754db17c78efb01468106aba32e30d70d2f4df
-
- 09 Jul, 2019 2 commits
-
-
Martin Kampas authored
Without the qmlimportscanner tool available, qmlplugindump fails (silently!) determining module dependencies, dumping unnecessarily components provided by those.
- 16 Apr, 2019 2 commits
-
-
chriadam authored
This commit exists to ensure a changelog entry exists for CI.
-
- 07 Mar, 2019 1 commit
-
-
Damien Caliste authored
-
- 15 Feb, 2019 1 commit
-
- 11 Jan, 2019 2 commits
-
-
pvuorela authored
-
pvuorela authored
On runtime the active dpi is compared to "General/BaseDPI" on QtQuick2.conf file to multiply configuration items value marked as scalable. That is done by having configuration item name appended with "Scaled", e.g. [QuickFlickable] FlickThresholdScaled=15 On MouseArea the old, not anymore used, configuration for press and hold timeout was removed. This commit can be squashed with earlier configuration support commit when rebased to newer Qt releasese: "Allow QtQuick2 parameters to be configured".
-
- 25 May, 2018 1 commit
-
-
Slava Monich authored
[qtdeclarative] Fix crash in ModelNodeMetaObject::emitDirectNotifies. Fixes JB#41922 See merge request !20
-
- 24 May, 2018 1 commit
-
-
Simon Hausmann authored
If we call get() on a model in a worker thread, we may end up creating a ModelNodeMetaObject (aka cacheObject). Subsequent mutation of properties may make us end up in emitDirectNotifies(). However since we can't have bindings in there, we should shortcut/suppress the notify emission, which we can do by checking ddata->context via qmlEngine(). The previous code crashed when qmlEngine() return a null pointer but QQmlEnginePrivate::get(const QQmlEngine *) would attempt to dereference the parameter. Started-by: Slava Monich<slava.monich@jolla.com> Change-Id: I880619c686436c053692faafa5dba2c96c2ace96 Reviewed-by:
Robin Burchell <robin.burchell@crimson.no> Reviewed-by:
Slava Monich <slava.monich@jolla.com>
-
- 30 Apr, 2018 3 commits
-
-
Pekka Vuorela authored
Only bug fixes so far and 5.6.4 cmake rules demand qtbase 5.6.4. This reverts commit ad66f10f.
- 27 Apr, 2018 2 commits
-
-
Pekka Vuorela authored
Hopefully fixing the few seen ListModel related crashes. Not including too many changes.
-
Pekka Vuorela authored
-
- 15 Mar, 2018 1 commit
-
-
Erik Verbruggen authored
The generated code for jump-on-strict-not-equal-undefined used the same logic (but with inverted conditions) as the equal case. For equality, one can jump to else if the value parts are not the same. So, for not-equal, if the value parts are the same, it would jump to the else block if they are the same. Meaning, an encoded int value of 0 (which is strict-not-equal to undefined) would end up being evaluated as equal. Task-number: QTBUG-66832 Change-Id: Id27bb44eccbf39608ae8cebab634c8bcd4c8adfc Reviewed-by:
Simon Hausmann <simon.hausmann@qt.io>
-
- 26 Feb, 2018 1 commit
-
-
Simon Hausmann authored
Assigning to a group property inside a property value source or interceptor as part of an "on assignment" is perfectly valid. That is because while "color" is a value type property, the on assignment means we're actually setting easing.type (in the example and test) on the property value source, not the color, and that one is a QObject. The same goes for interceptors. Conflicts: src/qml/compiler/qqmlpropertyvalidator.cpp src/qml/qml/qqmlvmemetaobject_p.h tests/auto/qml/qqmllanguage/tst_qqmllanguage.cpp Change-Id: I505a658977a578894d6dfb00bf5c65b41e42b12f Task-number: QTBUG-56600 Reviewed-by:
Michael Brasser <michael.brasser@live.com> (cherry picked from commit 2659c308792967322564b5088e0e21bb371e0283)
-
- 23 Feb, 2018 1 commit
-
-
Simon Hausmann authored
This is a regression introduced with commit 4876ea6a. Where we previously always returned the same JS object, we would afterwards return a new JS object for every invocation, which breaks reference comparison. As we store the JS wrapper for the list element in the QQmlData->jsWrapper we can avoid repeated allocations. In order for that wrapper to keep working after modifications (insertion, etc.) to the list model, we have to replace the static element index with a reference to the node model meta-object, which also has an element index that however is kept up-to-date by the list model itself. Conflicts: src/qml/types/qqmllistmodel_p_p.h Change-Id: I4368de6b6d86687fe96fbf73bd60b80b69d7b058 Task-number: QTBUG-52017 Reviewed-by:
Michael Brasser <michael.brasser@live.com> (cherry picked from commit 44a89492b49f23a975377795dbb7a48916cb5081) Reviewed-by:
Mitch Curtis <mitch.curtis@qt.io>
-
- 22 Feb, 2018 1 commit
-
-
Erik Verbruggen authored
This is a combination of 2 commits that went into 5.9. They cannot be cherry-picked however, because some c++11 constructs were used. Hence this combo commit, which is a squashed version of those two commits that have the c++11 bits replaced by Good Old boilerplate code. Original commit 1 (e29ffa17): Fix use-after-free when removing elements from a ListModel Detaching delegate instances from model items is done after the destruction of said model items. The problem is that after the model item is destroyed, it will emit a change/destroyed signal. As the delegate is still referencing the item, this will result in a use-after-free. To provent that, the items are kept around until after everyone (notably the delegate model) has been notified of the removal. [ChangeLog][Qt][Qml] Fix possible use-after-free when removing items from a ListModel through JavaScript. Original commit 2 (163c5157): Fix use-after-free when clear()ing all elements from a ListModel Same problem as the problem with remove(), so now clear will call into remove to do the correct thing. [ChangeLog][Qt][Qml] Fix possible use-after-free when clearing all items from a ListModel through JavaScript. Task-number: QTBUG-63383 Change-Id: I9a6bdf65da63b33833f18c80e74ad7bb93409627 Reviewed-by:
Simon Hausmann <simon.hausmann@qt.io>
-
- 13 Feb, 2018 1 commit
-
-
Simon Hausmann authored
This is a regression introduced with commit 3cc589c9, which in turn fixed a leak with QV4::QObjectWrapper objects. Unfortunately the allocate() call into the persistent (weak) value storage in the list model introduced a leak of the weak value itself. This is fixed by replacing the free standing weak value allocation with the use of the existing jsWrapper weak value in the declarative data (QQmlData). That weak value is freed property in the destroy() method of the QV4::QObjectWRapper. The extra QQmlData allocation is hidden behind a unified allocation, similar to what we do in void QQmlType::create(QObject **, void **, size_t) const. Task-number: QTBUG-66189 Change-Id: I5351e3e484542709a6b210e84aa19b14d28e11ad Reviewed-by:
Lars Knoll <lars.knoll@qt.io> (cherry picked from commit 22d43f74e264626d0c28654c42c91839f9de45b5) Reviewed-by:
Erik Verbruggen <erik.verbruggen@qt.io>
-