Commits (10)
-
Simon Hausmann authored
Use https and qt.io links. Change-Id: I089098317e38b52484a23bdfad128ef47eec8a21 Reviewed-by:
Robin Burchell <robin.burchell@viroteck.net>
1e44d36e -
Thiago Macieira authored
When compiled in release mode with GCC 6, QtQml crashes. This option gets works around the issue by instructing the compiler not to delete null pointer checks for pointers that the standard says cannot be null, yet apparently are. This is a temporary workaround until a proper solution is found. Change-Id: Id3aab65533904562a6cbfffd14501a185fc91179 Reviewed-by:
Lars Knoll <lars.knoll@theqtcompany.com>
18e77550 -
Edward Welbourne authored
As pointed out by Coverity (CID 22368). Change-Id: I67bdda3f747b68a0197a4cb2e2aa750aa322b6ba Reviewed-by:
Simon Hausmann <simon.hausmann@qt.io>
72ee8417 -
Liang Qi authored
Change-Id: I7d9e0c90645d856e501ff70d97d55ffd615a2e31
f1884164 -
Edward Welbourne authored
As Coverity (CID 22302) points out, qobject_cast<> can return NULL; if we don't get a document layout, then we have no frame decorations to add to it. Change-Id: I2cd428456b3a3b24a28a5dd18ce948a8e95d21cb Reviewed-by:
Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
ddb60df2 -
Ralf Nolden authored
Add a __cplusplus condition to an already existing OpenBSD defined part to activate the code only on older gcc compilers. Change-Id: Ied8719dc35bf203ecbadd1099d711c027722121c Reviewed-by:
Simon Hausmann <simon.hausmann@qt.io>
32e0c5f9 -
Liang Qi authored
Blacklisted or skipped broken and unstable test functions. Some are moved to tests/auto/qmltest-blacklist folder. Task-number: QTBUG-33723 Task-number: QTBUG-38290 Task-number: QTBUG-53778 Task-number: QTBUG-53779 Task-number: QTBUG-53780 Task-number: QTBUG-53781 Task-number: QTBUG-53782 Task-number: QTBUG-53785 Task-number: QTBUG-53793 Change-Id: I35594d0d054f4f5719f6549536a1fc5bd7e2518f Reviewed-by:
Simon Hausmann <simon.hausmann@qt.io>
38b11b7b -
Filippo Cucchetto authored
This reverts commit 9c8dab53 where commit e1400b5b was removed due to the breakage of QtLocation tests. After some hours of debugging it seems that the problem in QtLocation was due to filtering of mouse move events in QDeclarativeGeoMapItemBase. See QTBUG-52075 Task-number: QTBUG-52534 Change-Id: I00f002c1d6f60f74a148b5a6ac2b9f63e93718a9 Reviewed-by:
Paolo Angelelli <paolo.angelelli@theqtcompany.com> Reviewed-by:
Michal Klocek <michal.klocek@theqtcompany.com>
7039db48 -
Mitch Curtis authored
Change-Id: I2c73a4bdfa43200c52df33cec573a8799e4fe5e0 Reviewed-by:
Simon Hausmann <simon.hausmann@qt.io>
b6c64c2e -
Simon Hausmann authored
Since commit 91d6a63a a null JS value is mapped to a QVariant(VoidStar) to properly create null JS values when converting back again. However that broke the binding of values in the SQL database, where it ended up mapping null to an empty string. [ChangeLog][QtQml] Fix mapping of null JS values to null SQL values instead of empty strings. Task-number: QTBUG-53412 Change-Id: Icf1fea4674e9dd8bb5313e3770ed2d3f99849987 Reviewed-by:
Robin Burchell <robin.burchell@viroteck.net>
6d63e3ba
Showing
File moved
File moved
File moved
File moved
File moved
File moved
File moved
File moved
File moved