| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Now that we know the type and whether it should be native, it can
be all done in the base class to reduce a lot of code duplication.
Change-Id: I7d7d7057fa499df75b72914d2b505bfa0288048d
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
| |
Change-Id: Id1699a6045eb9066a80ebdbb3cb5d3a01e58a36f
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
| |
Change-Id: I42b5e403e6cb16e607d9ce0d0e9f624b150bec03
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
| |
Change-Id: I4b65c7623a34d016243e626146437d2fa20fd93b
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
| |
A more generic replacement for MessageDialog.clickedButton.
Change-Id: I060f70a48ab258485e3155188e483c4cf24210e0
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
| |
Change-Id: I6bccfebcbb32dcafeea0814d88f7882857a62a85
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
| |
Change-Id: Ie963cb5c082b49205f7b7244ace3b88254ec37c7
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
| |
To be more in line with QtQuick.Dialogs 1.x.
Change-Id: Ic512222a88a376ebc142563dceccbbb1c3b98a75
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
|
| |
This is similar to what MessageDialog from QtQuick Dialogs 1.x does,
and evidently very convenient and intuitive to use.
Change-Id: I8f7e0f98cfbc256e0dd398471b63ecf04d884314
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Available categories:
- qt.labs.platform.dialogs
- qt.labs.platform.menus
- qt.labs.platform.tray
The output shows which implementation is used. Example:
$ QT_LOGGING_RULES=qt.labs.platform.*=true ./texteditor
qt.labs.platform.menus: MenuBar: QCocoaMenuBar(0x7fe27bdf7730)
qt.labs.platform.menus: Menu: QPlatformMenu(0x7fe27bdf8450)
qt.labs.platform.menus: Menu: QPlatformMenu(0x7fe27bdfa510)
qt.labs.platform.menus: Menu: QPlatformMenu(0x7fe27e500000)
qt.labs.platform.dialogs: FileDialog: QPlatformFileDialogHelper(0x7fe27e500f30)
qt.labs.platform.dialogs: FileDialog: QPlatformFileDialogHelper(0x7fe27e501ac0)
qt.labs.platform.dialogs: ColorDialog: QPlatformColorDialogHelper(0x7fe27e502920)
qt.labs.platform.dialogs: MessageDialog: QWidgetPlatformMessageDialog(0x7fe27e523b40)
qt.labs.platform.menus: Menu: QPlatformMenu(0x7fe27bcd9c30)
Change-Id: I07fc8b13f05f365337bc171149bb848639b3fbd0
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
|
| |
The clicked signal from the platform dialog cannot be wired to
the close slot. We must check the role and act accordingly.
Change-Id: I2cb9e106814f9b901d76dd79ff8eeeafe98d4d46
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Platform dialogs hold a shared pointer to an options structure.
Dialog implementations may access the options in various places
(eg. QGtk3FileDialogHelper::selectFile()) and seem to rely that
the options are not null at this point. Thus, pass the options
pointer right away on construction instead of unnecessarily
delaying to applyOptions(), to avoid potential crashes.
Change-Id: I14b0801eb58a9834867dd302a6610e64adeea0cd
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
Change-Id: I89f67fa4f620dc81dd9e7fe848f37ea5c12d5db7
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|