aboutsummaryrefslogtreecommitdiffstats
path: root/tests/manual/quickcontrols/menus
Commit message (Collapse)AuthorAgeFilesLines
* ContextMenu: add to text editing controlsMitch Curtis2025-02-281-29/+0
| | | | | | | | | | | [ChangeLog][Controls] TextField and TextArea now provide a ContextMenu by default. If you already have a custom context menu for these types, ContextMenu will not open its own on e.g. right click. Fixes: QTBUG-35598 Pick-to: 6.9 Change-Id: I0897a7ba5e1b5b6d5425c80cbc6f2550c904605b Reviewed-by: Mitch Curtis <[email protected]>
* Add ContextMenuMitch Curtis2024-12-241-6/+1
| | | | | | | | | | | | | | | This is an attached type that provides a way to open a context menu in a platform-appropriate manner. [ChangeLog][Controls] Added ContextMenu. ContextMenu can be attached to any item in order to show a context menu upon a platform-specific event, such as a right click or the context menu key. Fixes: QTBUG-67331 Pick-to: 6.9 Change-Id: I225a8f498cc5bc18d36c3dc4cf481ef5ef95cd88 Reviewed-by: Jan Arve Sæther <[email protected]> Reviewed-by: Shawn Rutledge <[email protected]>
* QQuickMenu: respect Qt::AA_DontUseNativeMenuWindowsRichard Moe Gustavsen2024-07-033-0/+29
| | | | | | | | | | Now that we enable native menus by default for the macOS style, we also need to make sure that we actually respect the Qt::AA_DontUseNativeMenuWindows. Pick-to: 6.8 Change-Id: I2a02b5528110a4e0514fb53c0673653f0086dfe8 Reviewed-by: Mitch Curtis <[email protected]>
* Correct license for tests fileLucie Gérard2024-06-273-3/+3
| | | | | | | | | | | | According to QUIP-18 [1], all tests file should be LicenseRef-Qt-Commercial OR GPL-3.0-only [1]: https://contribute.qt-project.org/quips/18 Pick-to: 6.8 Task-number: QTBUG-121787 Change-Id: I50964da74d6360bb88fc468765f6362ad39d20d1 Reviewed-by: Ulf Hermann <[email protected]>
* menus manual test: add SubSub menusRichard Moe Gustavsen2024-06-211-0/+10
| | | | | | | | | | Its nice to be able to test that you can still e.g hover the root menu, even when a subsub menu is the active popup. Pick-to: 6.8 Change-Id: Ibf76770a13c41f4712187daeb793439c83730db9 Reviewed-by: Mitch Curtis <[email protected]>
* Menus manual test: update popupType comboboxRichard Moe Gustavsen2024-06-191-6/+15
| | | | | | | | | | | Update the manual test to reflect that we no longer have a Popup.Default option. Also, after seeing some warnings, add a popupType() function, to improve type safety. Pick-to: 6.8 Change-Id: I70c4a52d776522541251bb0b2ab260b735d49171 Reviewed-by: Mitch Curtis <[email protected]>
* Replace AA_DontUsePopupWindows with Popup::popupTypeOliver Eftevaag2024-05-301-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The application attribute approach has some weaknesses which makes it less suitable, than simply having a property which can be set per instance of Popup. In addition, given just how many of our own tests that are failing, when changing the default behavior of popup, it`s a much safer approach to introduce this feature as an opt-in, in the beginning. We can instead potentially modify the behavior of PopupType::Default in the future, when we feel that it's less risky to do so. To give more context to why the AA approach is bad: - The AA is too grandiose of a solution, which adds an arbitrary limitation of not allowing mixing of in-scene popups and popup windows. This also affects 3rd party libraries. - It causes inconveniences when styling the various popup types. Dialog, for instance, has a title property, which should be shown in the window title, and not inside the popup window. - It also makes it less flexible for potential future changes. We've learned that this change is riskier, than initially expected, since the qobject and visual hierarchy of popup objects are different when using popup windows, and tests that simulate events, will need to send the events to a different window. The introduction of the PopupType::Default value, allows us to, for instance, add a property later in ApplicationWindow, or somewhere else, to change the behavior of PopupType::Default. Meaning that we can still add a more grandiose API, that affects the behavior of multiple popup instances, if we think it's too cumbersome for developers to add `popupType: Popup.Window` to all popup instances. Task-number: QTBUG-121363 Change-Id: I544da820261607621a9b9ad5c4c9679e676e44a0 Reviewed-by: Shawn Rutledge <[email protected]>
* manual test, menus: use Popup.popupTypeRichard Moe Gustavsen2024-05-303-27/+32
| | | | | | | | Now that Popup has a popupType API, use it in favor of AA_DontUseNativeMenuWindows. Change-Id: I6b666e9c36f5d8b95701ac6a94c29ac3d7a6d206 Reviewed-by: Mitch Curtis <[email protected]>
* Menus test: inform when a restart is neededRichard Moe Gustavsen2024-05-291-1/+11
| | | | | | | | | | | Changing whether or not to use a native menu bar requires setting AA_DontUseNativeMenuBar. But this will only take effect the next time the app is started. So inform about this, since it can otherwise be quite confusing for the "tester". Change-Id: Ie37b9ec0cc66660548ea13cb383440536e6fd707 Reviewed-by: Mitch Curtis <[email protected]>
* menus: fix quitting with Cmd+Q on macOSMitch Curtis2024-05-201-1/+5
| | | | | | | | It seems the Quit menu bar item steals the shortcut, so we have to do something with it. Change-Id: I3831c8bc99728773e22284232d7ab54ba6eb117f Reviewed-by: Richard Moe Gustavsen <[email protected]>
* Menus manual test: open context menu on mouse press or touch long-pressShawn Rutledge2024-05-161-4/+14
| | | | | | | This enables testing the drag-press-release gesture. Change-Id: I953fee1f891b2ac907a5a69ca98f720496e7ed91 Reviewed-by: Richard Moe Gustavsen <[email protected]>
* manual test, menus: add support for more test casesRichard Moe Gustavsen2024-05-101-0/+34
| | | | | | | | | | | Add more logic to the manual test to test: 1. changing the delegate 2. changing the title of a menu in the menu bar 3. using sub menus 3. using checkable menu items in the menu bar menus Change-Id: I6a7256fb368a3557837c0448a6ddc895bb24924d Reviewed-by: Mitch Curtis <[email protected]>
* Add support for icons to native menusMitch Curtis2024-05-064-0/+21
| | | | | | Task-number: QTBUG-69558 Change-Id: I9486f474dd386061636c326b508c20848ebab807 Reviewed-by: Richard Moe Gustavsen <[email protected]>
* menus: add shortcutsMitch Curtis2024-04-231-3/+21
| | | | | | Task-number: QTBUG-69558 Change-Id: I440fb7caff125d2417fb648df667219e42b375bc Reviewed-by: Richard Moe Gustavsen <[email protected]>
* Menu, MenuBar: remove requestNative and rely solely on app attributesMitch Curtis2024-04-177-94/+136
| | | | | | | | | | | | | | | | | | | | | | | | It was decided that we'll have two attributes: - AA_DontUseNativeMenuBar - AA_DontUseNativeMenuWindows Setting AA_DontUseNativeMenuWindows only affects windows we create (context menus, combobox menus, menus of non-native menu bars). So, setting AA_DontUseNativeMenuWindows restores Qt to today's behavior. But we can't control the windows of native menu bars, so if you don't want those to be native, you have to set AA_DontUseNativeMenuBar just like today. By removing requestNative, we also effectively default to native menus and menu bars, as the attributes are not set by default. [ChangeLog][Controls][Important Behavior Changes] Menu and MenuBar now use native menus by default on platforms where they're supported. Task-number: QTBUG-69558 Change-Id: Ia917c2f820634def0cf815aa8ca8895ca79db75d Reviewed-by: Richard Moe Gustavsen <[email protected]>
* Manual test, menus: add support for testing menubarRichard Moe Gustavsen2024-02-231-35/+123
| | | | | Change-Id: Id8e55e3f3b05aab0ab02452452e08783181a7be8 Reviewed-by: Mitch Curtis <[email protected]>
* QQuickMenuBar: respect AA_DontUseNativeMenuBarRichard Moe Gustavsen2024-02-221-0/+1
| | | | | | | | If the application sets AA_DontUseNativeMenuBar, it should override the requestNative property. Change-Id: Id69c09310d61e9a59746e32435a97742e28c80d3 Reviewed-by: Mitch Curtis <[email protected]>
* Menu: fix native checkable MenuItems (without an Action) not checkingMitch Curtis2024-02-121-1/+1
| | | | | | | | | | | Not only do we need to ensure that the checked state changes so that syncing the MenuItem to the native menu item works, but we should also emit the same signals that would be emitted if the user had actually interacted with the MenuItem. Task-number: QTBUG-69558 Change-Id: I0ac1d16c0f84da1d9f6639b724ba47ea124da59a Reviewed-by: Richard Moe Gustavsen <[email protected]>
* Menu: support adding MenuItem to native menuMitch Curtis2024-02-121-3/+7
| | | | | | | | | | | | | Originally the plan was to revert to a non-native menu when MenuItem was used, but now that we always create the non-native items regardless, we shouldn't need to do that. Checkable MenuItems do not currently work. This will be implemented in a follow-up commit. Task-number: QTBUG-69558 Change-Id: I7238dad89e478f7cc664738fb6036787e0193dab Reviewed-by: Richard Moe Gustavsen <[email protected]>
* Menu: allow setting (but not always respecting) requestNativeMitch Curtis2024-02-121-0/+5
| | | | | | | | | | We can allow this to be set while the menu is a sub-menu and/or visible, and instead wait until it is re-opened to take the change into effect. Task-number: QTBUG-69558 Change-Id: Ie79819609950c2f6432e55c09d21dce7e8d9b220 Reviewed-by: Richard Moe Gustavsen <[email protected]>
* Menu: respect requestNative changesMitch Curtis2024-02-121-9/+15
| | | | | | | | | | This patch ensures that a native menu is created (or destroyed) when requestNative is set, if possible. Task-number: QTBUG-69558 Change-Id: Ic7f8826bf4def66e66932618767a81ad19e114f0 Reviewed-by: Richard Moe Gustavsen <[email protected]> Reviewed-by: Mitch Curtis <[email protected]>
* Implement native menu separatorMitch Curtis2024-02-121-1/+4
| | | | | | Task-number: QTBUG-69558 Change-Id: I3da4509a722ec5ee4620111fc9482e6d688fdd9d Reviewed-by: Richard Moe Gustavsen <[email protected]>
* Add disabled Actions to menus manual testMitch Curtis2024-01-221-0/+20
| | | | | | Task-number: QTBUG-69558 Change-Id: I6517a679a3fb80cda577971425e582c8bab5eba6 Reviewed-by: Richard Moe Gustavsen <[email protected]>
* Add checkable Actions to menus manual testMitch Curtis2024-01-221-7/+16
| | | | | | | | | | This can't reliably be auto-tested because we can't interact with menu items with the mouse, and there's no way to know if a native menu is focused in order to interact with it via keyboard. Task-number: QTBUG-69558 Change-Id: I21134743ccc64ca1bf99f085f09c00d66a3ca3dc Reviewed-by: Richard Moe Gustavsen <[email protected]>
* Menu: get native sub-menus workingMitch Curtis2024-01-171-14/+66
| | | | | | Task-number: QTBUG-69558 Change-Id: Iee7393a00bcaf4f25f579ec60ebfecf7ef357761 Reviewed-by: Richard Moe Gustavsen <[email protected]>
* Add menus manual testMitch Curtis2024-01-175-0/+279
This gives us a convenient way to manually test native menus, which can't be fully auto-tested. Task-number: QTBUG-69558 Change-Id: I045eef8d30eb8f130f6e4ba4787a9d0ad84c109f Reviewed-by: Richard Moe Gustavsen <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2025-05-14 08:12:55 +0000