- 28 Nov, 2016 - 1 commit
-
-
Oswald Buddenhagen authored
Change-Id: Ifd63ae7b54938ce8c85150ef0b49f65ea214d05d
-
- 06 Nov, 2016 - 1 commit
-
-
Oswald Buddenhagen authored
the CI obtains them from the qt5 super repo nowadays. Change-Id: Icdcaa7ad856eb493448398f9180ecc4b642262d9 Reviewed-by:
Jędrzej Nowacki <jedrzej.nowacki@qt.io>
-
- 10 Aug, 2016 - 1 commit
-
-
Maurice Kalinowski authored
Change-Id: I85b2baec60f700a9246e6ce177e7079b8e791ad2 Reviewed-by:
J-P Nurmi <jpnurmi@qt.io>
-
- 09 Aug, 2016 - 1 commit
-
-
J-P Nurmi authored
See qtdeclarative commit ebf07c3f for more details. Task-number: QTBUG-55179 Change-Id: Ie7d855396148c892077381666e0200180dda02bd Reviewed-by:
Liang Qi <liang.qi@qt.io>
-
- 18 Jun, 2016 - 1 commit
-
-
Sze Howe Koh authored
See http://comments.gmane.org/gmane.comp.lib.qt.devel/25771 Change-Id: I1612c3725ba38b7a1e5840810f565e173281f700 Reviewed-by:
Lars Knoll <lars.knoll@qt.io>
-
- 31 May, 2016 - 1 commit
-
-
Liang Qi authored
Change-Id: I60fa2daaf08b89567bcc645a5dc0654720273418
-
- 25 May, 2016 - 1 commit
-
-
Liang Qi authored
error: no matching function for call to 'QQmlComponentPrivate::initializeObjectWithInitialProperties(QV4::ScopedValue&, QQuickItem*&)' (cherry picked from commit 6fe784b9 ) Change-Id: Ic3db50f44912d9e5cdb71f6712fff554fc76505e Reviewed-by:
Simon Hausmann <simon.hausmann@qt.io>
-
- 20 May, 2016 - 1 commit
-
-
Liang Qi authored
error: no matching function for call to 'QQmlComponentPrivate::initializeObjectWithInitialProperties(QV4::ScopedValue&, QQuickItem*&)' (cherry picked from commit 6fe784b9 ) Change-Id: Ic175bb290dcfbb944fee7545d3b97be8a202896a Reviewed-by:
J-P Nurmi <jpnurmi@qt.io>
-
- 19 May, 2016 - 1 commit
-
-
Oswald Buddenhagen authored
Change-Id: I54cd96a80f61c9be728b3e59c43dcd276d174bea
-
- 12 May, 2016 - 1 commit
-
-
Topi Reinio authored
Examples in binary packages now directly match the install path. Change-Id: Ia37e1223008592f0d410155611e41918825f55fd Task-number: QTBUG-52953 Reviewed-by:
Antti Kokko <antti.kokko@qt.io>
-
- 06 May, 2016 - 1 commit
-
-
J-P Nurmi authored
Use the pre-defined macro. Change-Id: Ie2b5a93f0b6ed16276b80fcb9e118a49a055194c Task-number: QTBUG-53208 Reviewed-by:
Simon Hausmann <simon.hausmann@theqtcompany.com>
-
- 02 May, 2016 - 1 commit
-
-
J-P Nurmi authored
Change-Id: I52cf46dab51382c9184a9dda7107154e52df74ef Task-number: QTBUG-52731 Reviewed-by:
J-P Nurmi <jpnurmi@qt.io>
-
- 27 Apr, 2016 - 3 commits
-
-
J-P Nurmi authored
Change-Id: I40d3b50153bead01150284b2a5c3f45dbe486462 Task-number: QTBUG-52731 Reviewed-by:
J-P Nurmi <jpnurmi@qt.io>
-
J-P Nurmi authored
Also found with Valgrind. Change-Id: Ibde7714e15296d36f4cf34b5d004322531138271 Task-number: QTBUG-52731 Reviewed-by:
J-P Nurmi <jpnurmi@qt.io>
-
J-P Nurmi authored
QQuickWindow::windowChange() is emitted from QQuickWindow destructor. This means, that QQuickApplicationWindow destructor has been already executed, and thus, QQuickApplicationWindowPrivate has been deleted. The issue was found with Valgrind. A workaround is to explicitly reset the d-pointer so that we can test whether it's still valid. Change-Id: I82d388d8aae18886ec92ef09c745a1c045f46a39 Task-number: QTBUG-52731 Reviewed-by:
J-P Nurmi <jpnurmi@qt.io>
-
- 26 Apr, 2016 - 1 commit
-
-
Nikita Krupenko authored
The 1px padding at the top and at the bottom are unnecessary. Change-Id: I0d6d2a5753cf987ab2782afa5d5dd2bb2c739568 Reviewed-by:
J-P Nurmi <jpnurmi@qt.io>
-
- 20 Apr, 2016 - 1 commit
-
-
Nikita Krupenko authored
Task-number: QTBUG-52631 Change-Id: Ib1649f44cdbc14770b1759ef7f4d7ea92f148cc1 Reviewed-by:
J-P Nurmi <jpnurmi@qt.io>
-
- 19 Apr, 2016 - 1 commit
-
-
Mitch Curtis authored
Change-Id: Ib04e79d72c37fa4507517da2d3b1c28ccd73eaed Reviewed-by:
J-P Nurmi <jpnurmi@qt.io> Reviewed-by:
Venugopal Shivashankar <venugopal.shivashankar@digia.com> Reviewed-by:
Topi Reiniö <topi.reinio@theqtcompany.com>
-
- 16 Apr, 2016 - 2 commits
-
-
Nikita Krupenko authored
Change-Id: Ia0b2134e4de48ca595d63456586e471c46151ce8 Reviewed-by:
J-P Nurmi <jpnurmi@theqtcompany.com>
-
Nikita Krupenko authored
Change-Id: I7c3cdbbe02c71c5341684c3d9da9f1d9b0222136 Reviewed-by:
J-P Nurmi <jpnurmi@theqtcompany.com>
-
- 13 Apr, 2016 - 3 commits
-
-
Thomas Hartmann authored
Those have to be manually added until dependecies work in Qt Creator. Change-Id: I416065bd3a1d074bd7f5119cfc635a73e384f354 Reviewed-by:
Marco Benelli <marco.benelli@theqtcompany.com> Reviewed-by:
Tim Jenssen <tim.jenssen@theqtcompany.com>
-
Nikita Krupenko authored
Change-Id: Ie3e1808057af370f3f6a923a8a56709dd80223b8 Reviewed-by:
J-P Nurmi <jpnurmi@theqtcompany.com>
-
Nikita Krupenko authored
Change-Id: I35c3a15d17a15945ccbfa5eeb4359c7c5be3facf Reviewed-by:
J-P Nurmi <jpnurmi@theqtcompany.com>
-
- 12 Apr, 2016 - 1 commit
-
-
Thomas Hartmann authored
The '' confuses the designer. We will fix this but for now I change it to "". Change-Id: Ief4cfa3250e1dd1428dd972a7a10c5f6bd417033 Reviewed-by:
Thomas Hartmann <Thomas.Hartmann@theqtcompany.com>
-
- 11 Apr, 2016 - 1 commit
-
-
J-P Nurmi authored
Change-Id: Id78ef819c56d4639c33e7b4823c2c2600486befa Reviewed-by:
Mitch Curtis <mitch.curtis@theqtcompany.com>
-
- 01 Apr, 2016 - 1 commit
-
-
Joni Poikelin authored
Padding was not taken into account when calculating the new position, which caused there to be small offset between the mouse press and the resulting handle position by the amount of padding used. Task-number: QTBUG-52233 Change-Id: Ibd8c4375b030a27a6124aefc4bc9af570d14d3a9 Reviewed-by:
Mitch Curtis <mitch.curtis@theqtcompany.com>
-
- 23 Mar, 2016 - 1 commit
-
-
J-P Nurmi authored
The following comment in QQmlDelegateModel::object() helped to find a solution ie. using createdItem() instead of initItem(): If asynchronous is true or the component is being loaded asynchronously due to an ancestor being loaded asynchronously, item() may return 0. In this case createdItem() will be emitted when the item is available. [...] Change-Id: If3bf8e60834534ca07c8db8f502f4f11969057e8 Task-number: QTBUG-51972 Reviewed-by:
Mitch Curtis <mitch.curtis@theqtcompany.com>
-
- 22 Mar, 2016 - 2 commits
-
-
Edward Welbourne authored
Subjects each *.png file that matched grep -law "sRGB" to: pngcrush -ow -brute -rem allb -reduce -force Change-Id: I40e902a2ddff05684ff90b178728c562c2cd8cd1 Reviewed-by:
Topi Reiniö <topi.reinio@theqtcompany.com>
-
J-P Nurmi authored
tst_tooltip revealed a bug that QQuickPopupPositioner wasn't cleaning up its ancestor listeners properly. When QQuickPopup was destructed, it left a listener on the window root item. When the root item got later destructed, it tried to call a listener (the popup) that was already deleted. Change-Id: If041458da24be927f0bad19b9549dcabd1931977 Reviewed-by:
Mitch Curtis <mitch.curtis@theqtcompany.com>
-
- 21 Mar, 2016 - 1 commit
-
-
J-P Nurmi authored
Change-Id: I09f974a00a5a2a8f14645ff5d9bfbd6bad03d324 Task-number: QTBUG-51990 Reviewed-by:
Mitch Curtis <mitch.curtis@theqtcompany.com>
-
- 17 Mar, 2016 - 4 commits
-
-
J-P Nurmi authored
The idea of the "modalPopups > 1" check was to avoid calling QQmlProperty::write(), but it missed the fact that one modal popup might be still closing while a new modal popup is already opened. Thus, there's temporarily 2 modal popups visible, and we must transition the overlay background according to the state of the last shown modal popup. Change-Id: If25d83ccaa5adc29a9bc8d660f41fb66f90fb167 Task-number: QTBUG-51916 Reviewed-by:
Mitch Curtis <mitch.curtis@theqtcompany.com>
-
Nikita Krupenko authored
This fixes colors for checked switch dark theme and raised highlighted button in both themes. Change-Id: I3c485fb1b779104d6d7f682921b34cb535312f7c Reviewed-by:
Mitch Curtis <mitch.curtis@theqtcompany.com>
-
J-P Nurmi authored
The last one in the series of making Popup inherit its properties from the parent window instead of the parent item. The same change was done for font and style already. Change-Id: I7024cce13f501e92024e9110e87ed33bbae6533d Task-number: QTBUG-50984 Reviewed-by:
Mitch Curtis <mitch.curtis@theqtcompany.com>
-
J-P Nurmi authored
Don't access QQuickPopupItem while being destroyed. The popup item is deleted in QQuickPopup destructor, which is the parent of QQuickStyle that is attached to a popup. We don't need to remove the listener in this case. Change-Id: I0e0dba533b3b1299eb0d266c92f3070bb193c6c9 Reviewed-by:
J-P Nurmi <jpnurmi@theqtcompany.com>
-
- 16 Mar, 2016 - 1 commit
-
-
Nikita Krupenko authored
According to Android sources, ToolButton has the same font, as other buttons and checkable controls use default (system) font. Also, set proper size for default font. Change-Id: I355ab57ef476918bab346538fefbd6c0209d2221 Reviewed-by:
J-P Nurmi <jpnurmi@theqtcompany.com>
-
- 15 Mar, 2016 - 4 commits
-
-
J-P Nurmi authored
Change-Id: I80bd45244077cd75f24c4ca1af6485f4c6a23b39 Task-number: QTBUG-50984 Task-number: QTBUG-51696 Reviewed-by:
J-P Nurmi <jpnurmi@theqtcompany.com>
-
J-P Nurmi authored
The decision to make popups inherit theme & accent from its parent item was driven by ComboBox. However, in many cases it has an undesired side effect, so we've changed Popup to inherit its style attributes from the parent window instead, just like we did for fonts. The only exception to this is ComboBox, where the popup is an integral part of the control. This special case is now handled in the respective style implementation. A concrete example is that we can now specify dark theme by default for Material style ToolBar to get a better matching light text against the colorful background. In Gallery, this won't effect the options menu, which is a child of a ToolButton. The menu retains light theme along the rest of the application. Change-Id: Ibdc8fcf5b5fa258d853410a9b40368472424a8c6 Reviewed-by:
Mitch Curtis <mitch.curtis@theqtcompany.com>
-
J-P Nurmi authored
This is a partial revert of "Fix style inheritance" (07e0dec2) and "Fix style inheritance for popups" (a3dddf04 ). These changes made things too complex. It's easier to revert back to the original, and then apply the new popup style inheritance rules in the next commit. Change-Id: I2842261999d258a709739ee48a78ca23a2a1092a Reviewed-by:
Mitch Curtis <mitch.curtis@theqtcompany.com>
-
J-P Nurmi authored
The default system font must not have explicit attributes that would mess with font inheritance. This is already handled by the QFont() default constructor, but we must do it ourselves when we call QPlatformTheme::font(SystemFont) directly. Change-Id: Ia52e135411618e72cbf4618cffb9eec7924dc612 Task-number: QTBUG-50984 Task-number: QTBUG-51696 Reviewed-by:
J-P Nurmi <jpnurmi@theqtcompany.com>
-
- 11 Mar, 2016 - 1 commit
-
-
J-P Nurmi authored
Change-Id: I0daf4eb22d879e0b3e52ff16c9dd7b30a617001f Task-number: QTBUG-50984 Task-number: QTBUG-51696 Reviewed-by:
Liang Qi <liang.qi@theqtcompany.com>
-