summaryrefslogtreecommitdiff
path: root/src/dialogs/DefaultMessageDialog.qml
Commit message (Collapse)AuthorAgeFilesLines
* Unify license header usageAntti Kokko2016-02-041-12/+15
| | | | | | | Update old header.LGPL3 to header.LGPL Change-Id: I3c851bc24da89f6300b94199387d1adf16ca4f48 Reviewed-by: Lars Knoll <lars.knoll@theqtcompany.com>
* Dialogs: update license headersJ-P Nurmi2015-02-111-31/+27
| | | | | | Change-Id: I1abdce308929507416b5f24b4442d0b978886a46 Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@theqtcompany.com> Reviewed-by: Shawn Rutledge <shawn.rutledge@digia.com>
* Dialogs: added private maximumDimension property for initial sizeShawn Rutledge2014-10-131-1/+1
| | | | | | | | | | | The Screen.attached property does not know which screen will be used until the dialog is shown, but we need to know how big the desktop is before it is shown in order to constrain a reasonable dialog size, before the Flow lays out the buttons. Otherwise it will be too tall. Task-number: QTBUG-41734 Change-Id: I44349fab4ad0254d2c6faf30c759fb9e52eebf03 Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
* DefaultMessageDialog: ensure contentColumn initial widthShawn Rutledge2014-10-101-6/+3
| | | | | | | | | | | anchors seem to be applied after the Flow does its initial layout, but the Flow needs to know how wide it will be. The direct width binding is easier to calculate and applied earlier. Task-number: QTBUG-41734 Change-Id: I6232ef5ec82396f271a38f1068bc453872fedb35 Reviewed-by: Liang Qi <liang.qi@digia.com> Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
* Dialogs: Use native rendering on non-mobile platformsShawn Rutledge2014-10-081-0/+4
| | | | | | | | | Follow the same rule as in QtQuick.Controls: change 332ef31f0d1645eded5588729176134bbdcd38a2 Task-number: QTBUG-41734 Change-Id: I6d80e0312d3986b90952e43ffbddec1fe007fddb Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
* Dialogs: add qsTr() wrappers to all QML strings for translationv5.4.0-alpha1Shawn Rutledge2014-09-051-20/+20
| | | | | Change-Id: If5304902f7167df56266542969723481477a7ba9 Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
* Bump QtQuick.Controls import version to 1.2J-P Nurmi2014-04-071-1/+1
| | | | | Change-Id: Idc0b93cbfc2fe23e8be3bcaece672d06555a81f6 Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
* Import QtQuick 2.2J-P Nurmi2014-04-071-1/+1
| | | | | Change-Id: Ifc9719ec6fbbd80b866c01eebc471d0ed121bd16 Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
* MessageDialog: press escape or titlebar close button to dismissShawn Rutledge2014-02-281-0/+4
| | | | | | | | | | | QMessageBox is a bit special compared to other dialogs, but we don't need it to be so special in QtQuick.Dialogs. Also on OSX, cmd-period will dismiss the dialog, regardless whether it is a QMessageBox or the QML implementation. Task-number: QTBUG-36227 Change-Id: I5dd43080600e9c3774990190bb401291efb8e742 Reviewed-by: Liang Qi <liang.qi@digia.com>
* move QtQuick.Dialogs from qtdeclarative to qtquickcontrolsShawn Rutledge2014-01-031-0/+316
This will enable using Controls in the QML dialog implementations. For now, Controls are used only as drop-in replacements for the Button, Checkbox, and TextField which were custom implementations in the qtdeclarative module before. Change-Id: Ic79e9e8e5715a72ce51f4c724bfdfd33653300f2 Reviewed-by: Liang Qi <liang.qi@digia.com>
View Lorry Controller Status