| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
Add 'type' property to QtMenuBase (not exposed to QML explicitly,
but is the base class for all things menu). Useful to inspect menu items
after creation, for instance. Also, Menu gets addSeparator() and
addMenu() functions.
Since the Iterator type has been merged to QML, tst_menu now uses it.
Change-Id: I4a2f43ecce6671885e523d720e4e1315eca8616e
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
- minor change to Brief statement
- reword options for use context for menu
- removed spaces at end of some lines
- replaced "like" with "such as"
Change-Id: Ib529c03da12d0a463a72ebf0e7a9e311ff3ba29e
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
|
| |
|
|
|
|
| |
Change-Id: If9df032c76e36f385aacd30cc31d6f02574c6f11
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>
|
| |
|
|
|
| |
Change-Id: Ib0b1445593ff48df56cd8d4d20122880c2dacca5
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
|
| |
|
|
|
|
|
| |
... unless it has a submenu, of course.
Change-Id: I1b114f75d60fdd36ae90cbe96184c9a63495c65f
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
|
| |
|
|
|
|
|
| |
Used the same pattern as earlier with Menu.
Change-Id: Id7a2d791516ba6d827e90c3b3e11f97dd326ccd5
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
|
| |
|
|
|
| |
Change-Id: I98c4c6aa39f9a947f0610ac976ed74447252d06b
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
|
| |
|
|
|
|
|
|
| |
Note that currently, invisible Menus in MenuBars are not supported
because of the QPA backend. To be decided whether we want this...
Change-Id: Ide01c0ddc12f07969a5466a77b5c5c67b265ec87
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
|
| |
|
|
|
| |
Change-Id: Ieba2816190fc08bd2ec6410c4eb99e6557ab6206
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
|
| |
|
|
|
|
|
|
| |
Also removed Menu.visibleParent since it had no apparent use. Likewise,
trigger(), and the triggered() signal are now only in MenuItem.
Change-Id: Ide194505664c60906019422a503b189250d6a86e
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
|
| |
|
|
|
| |
Change-Id: Ic018c0d9c61ddf6fdf05750bf172cf5e306d0508
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
|
| |
|
|
|
| |
Change-Id: I1a7eff1a92e99e12369dd1e5a763c011350f381b
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
|
| |
|
|
|
| |
Change-Id: I4423f29d9c678d3432732ddf612042446e196869
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
|
| |
|
|
|
|
|
|
|
| |
This demanded some code refactoring, and the introduction
of the parent menu property. Updated auto-tests too.
Change-Id: I3d9070b0a1a76d6c174ccf13965d30413f23aadd
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
Reviewed-by: Caroline Chao <caroline.chao@digia.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some limitations in MouseArea force us to abandon the "one mouse area
per menu item" implementation in favor of a menu-wide mouse area,
where we track the position changes to highlight the menu item under
the mouse cursor. This makes possible updating the highlighted menu
item while keeping the mouse pressed.
Also, we need to emit an extra mouse press event, from the menu popup
window, so that the menu mouse area will receive any mouse release
event the user may have triggered. This is because the initial mouse
press event popping up the menu was made in another window, and
MouseArea would only emit 'released' signals if the released button
was already pressed.
Change-Id: Id10dd61fcf9e38ef3d34a61b7172301802e9646c
Reviewed-by: J-P Nurmi <jpnurmi@digia.com>
|
| |
|
|
|
|
|
|
| |
We want to use the same license as the other Qt modules.
QML files stay as BSD for now.
Change-Id: I10b1484f5ab0dfe2138ff7e045d0ecfd85556aa1
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
|
|
|
Change-Id: Icc61dbfc74cc2a303b9847e7d2c7ace4a9002046
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
|