| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Task-number: QTBUG-50003
Change-Id: I4809638c7ddaa4ca6fb99dbc734edb3641ecea05
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|\
| |
| |
| | |
Change-Id: I82c2b8d97d639e24147118a2ca6276ae70195b45
|
| |
| |
| |
| |
| |
| |
| | |
It should follow the stacking order of popups.
Change-Id: Id5664496c60e99bdf0aa4b2dc6a2c94dba2c756a
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Closed drawers sit visible at the window edge to be able to pull them
out. Don't block hover events when drawers are fully closed ie. when
their overlays are fully translucent.
Task-number: QTBUG-53419
Change-Id: I5bdbed5a2cf3ad6972634432ac79f7fbe5054b98
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-53419
Change-Id: I5c1ce684cff7954f9c011e991e3924741ad44367
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-53419
Change-Id: Ia3e23538bfba09454c9b473d8394814890ada150
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Make sure popup overlay dimmers gets destroyed when popups are closed,
and thus, re-parented out of the window overlay. The window overlay
item is hidden when there are no child items, so this fixes the issue
that the window overlay item was left visible after closing popups.
Change-Id: Id2ffe43b706ffcc5cda83abd75354ef04f893745
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
The asserts made qmlplugindump crash when run for QtQuick.Templates.
Change-Id: Ic18424555963640af806050f1e243e3b9bcfe993
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For src/imports/templates, simply running 'make qmltypes' does the job.
With src/imports/controls, we must help qmlplugindump a bit:
- pass the correct dependencies in a JSON file (or else qmlimportscanner
will find .impl imports, which qmlplugindump will fail to import as
stand-alone modules)
- merge with the plugins.qmltypes from templates to achieve proper type
hierarchy
The full command for dumping QtQuick.Controls 2.1 types, also seen at
the top of src/imports/controls/plugins.qmltypes:
qmlplugindump -nonrelocatable QtQuick.Controls 2.1 \
-merge ../templates/plugins.qmltypes \
-dependencies dependencies.json
Change-Id: I2d8a24e47e70dd8dd27a2f48fe640faeea8761e2
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
QQuickMaterialRipple compared the anchor item to QQuickWindow's
mouseGrabberItem to ensure that only mouse-pressed buttons would use the
press point, whereas key-pressed buttons would use the center point.
However, this does not work in case the mouse grab was stolen: when
first pressing an ItemDelegate and then dragging the containing ListView,
the ripple wave would always appear from the center point, not from the
press point as it should. Since QQuickAbstractButton::keyPressEvent()
sets the press point as the center of the control, the mouseGrabberItem
check can be simply removed.
Change-Id: Ic24e5e80c9d849f3fe2684013dd40b004ef55b57
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
The binding was copied from Button, and 'control.checked' condition
was accidentally left there. Such property doesn't exist in ComboBox.
Change-Id: I11b56e2da997ab2519a63527f58faff3d1bb4d8b
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
They are no longer specific to CheckBoxes, but used in most controls.
Change-Id: I404aeab706479d0b666529ebdb09caa6b8085cae
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
A .qrc file is no longer mandatory. One can list resources directly
in the RESOURCES variable.
Change-Id: I172b6cfa0a16c3296794888bd2f40a4273739c32
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ToolSeparator is used to visually distinguish between groups of items
in a toolbar by separating them with a line. It can be used in
horizontal or vertical toolbars.
Task-number: QTBUG-54862
Change-Id: Ie68e680510428ad19e7f80268063af07b61100eb
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These are no longer used now that the hovered and focused states are
visualized by the ripple background, and the pressed state by the
ripple waves and the elevation shadow.
Change-Id: Ia2d315c2d8b31e4fcd77534f6128584b9daeb8d8
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
qquicktumblerview_p.h:90:10: warning: 'updatePolish' overrides a member
function but is not marked 'override' [-Winconsistent-missing-override]
Change-Id: Iae769691c3aab5092bab497f8e0bc43a4972a32a
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-54764
Change-Id: Ie038161264c989853b2b6ec0bfceb09a1cd1195c
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-54764
Change-Id: Ie04c93a823745b6d0a85e0c80c91d4e7f77f6fcd
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
The press effect is visualized by the ripple background, so we
don't need to adjust the control background color when pressed.
Change-Id: Ic3acea4591d59f3045004b7e85a5b5bb9044c9f2
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Pressed buttons were way too dark, and ripples weren't even visible
for highlighted buttons. Now that we have ripples, we don't need to
use so many different color shades to present various button states.
Also, visualize the checked state with a little accented bar like
the Android ToggleButton does.
Change-Id: Id717b658bfe70ba211e4da5a6addc6e10a2df3e5
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: I84702195fa09af53697c987efd8c87afd429f3c4
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|\|
| |
| |
| | |
Change-Id: Idf19dd882ba3015be2afda6988cac1e95a4912fa
|
| |
| |
| |
| |
| | |
Change-Id: I9e393d3db42ba21ee2e1cd231bb91fd55bcace46
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
import "controls" was supposed to refer to a directory named
"controls".
Change-Id: I6e977354fa1ce01b1c14dda378d077b1003cb21a
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: Iec9a8126cf424925fbe74d1f4dfb6a1d55fc2e64
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| | |
Change-Id: I08030cab226c3e1f602e922fa1cad0a260e0c0ad
Task-number: QTBUG-54552
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Trigger ripples on press for flat buttons, on release for raised
buttons. Use highlighted (colored) ripple for highlighted (colored)
buttons, not for checked (not colored) buttons.
Change-Id: Ic7a6de070e568792d39cc20af35229517b7fd69e
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Model the Material style scroll bar after the Chrome OS scroll bar.
This adds a hover effect, and makes the transient timeout much longer
to make the scroll bars easier to use on desktop.
Task-number: QTBUG-50003
Change-Id: I5b1798e6c6b04482eab21d56e48935e2a9c69250
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
[ChangeLog][Controls] Added Dialog to provide convenience for handling
dialog popups. Dialog integrates with DialogButtonBox, and provides
convenient accepted() and rejected() signals.
Task-number: QTBUG-51090
Change-Id: I776516738b82c0e5726769c054d6f2a956fb616d
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: Ifa7ef9b0960494df917f9f60bf8d94cbee0f4661
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: I381d84c45cf6cd9b1209fd0d5c7441a9f7707664
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-50003
Change-Id: Ia17ac68adfda3babbc12b9c3484d8c9c74c736fb
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, it was casting the attachee object to an item and passing it as
a parent to the QObject constructor. When attached to a non-Item, it passed
a null pointer as a parent.
Change-Id: I45933e39e3080ab8e010fa3f7257fdffce4db685
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: Icf62245d16d9f7c2b3652eec267115b41916149b
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/quicktemplates2/qquickswipedelegate.cpp
tests/auto/controls/data/tst_swipedelegate.qml
tests/auto/controls/data/tst_textarea.qml
tests/auto/controls/data/tst_textfield.qml
Change-Id: I244f4ead4d14238c41db0bd965d7a2938f2ea8fc
|
| |
| |
| |
| |
| |
| |
| |
| | |
Otherwise the delegate's text doesn't change with height animations.
Task-number: QTBUG-54780
Change-Id: I4e253b807e4765732a80100fca102b6650527948
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
Adapted from Component::createObject() docs.
Change-Id: I53e44cfbcb4e4f1cc407e09d4ee90724526c9411
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| | |
Change-Id: I6af4f1a4517e79f2e34b0bbca401b0eefd0c6ff4
Task-number: QTBUG-54660
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| | |
Change-Id: I284b0d84363a172b2f11093b01157d00db69103a
Task-number: QTBUG-54658
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-54658
Change-Id: Ie8bb1fa6669c7dd1cd18199d01c773a1854edad4
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| | |
Change-Id: I7549509aef9a88af7e6a449bae52da273b0253d0
Task-number: QTBUG-54629
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The delayed/intercepted mouse press event must be passed first,
before letting the base class handle the double-click event.
Change-Id: I029d06b0b619f34bb7be13ae12b8904f2efe6b5b
Task-number: QTBUG-54615
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
While this is not a proper fix to the linked bug, debugging the issue revealed
that Drawer was way too eager to grab touch outside the drawer. It would not
do anything with the events until finger reached the drawer panel, so it's
completely unnecessary to steal the press far outside.
Change-Id: I76ff778b939327632cb29203db1c24e05c2a1a75
Task-number: QTBUG-53929
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| | |
Change-Id: I3fb5434722dd5d6cd744e3d853a5a15e52bf03d0
Task-number: QTBUG-54645
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Gets the same ripple/hover effect for free.
Task-number: QTBUG-54764
Change-Id: Ie741fa0c96293fde90c55b845d8ce5cccce3481f
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
MenuItem looks very similar to ItemDelegate, so I unthoughtfully made
both trigger ripples on release. However, Menus typically close when
menu items are triggered, so triggering ripples on release means the
ripples are never shown. For what it's worth, Android 6 also shows
ripple effects on release for list items, and on press for menu items.
Task-number: QTBUG-54764
Change-Id: I3bc362dbe4b890908ecb38a19edc804a5deb31e6
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
The layouting code broke in commit aa823b2 that fixed the build
after item change listener changes in qtdeclarative.
Change-Id: Ife3c598c6aca03f0aebe1fdf32f5ca412de62f0d
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These allow users to detect when non-interactive left/right/behind
items are being pressed and clicked.
[ChangeLog][SwipeDelegate] Added swipe.pressed and swipe.clicked()
for detecting when non-interactive left/right/behind items are pressed
and clicked.
Change-Id: I858f0a8e4f85b3f80f93eb4f1680d8e121acdd41
Task-number: QTBUG-54651
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is mostly useful for being able to use either push or pop
transition for replace operations, but there doesn't seem to be
any reason to limit the others. So, now it's able to run any of
the push/pop/replace transitions (or none with "immediate") for
any push/pop/replace operation.
[ChangeLog][StackView] Made it possible to choose the visual
transition type for any operation. This allows using for example
push and pop transitions with replace(), which allows implementing
an "infinite" back and forward navigation pattern while keeping
the amount of instantiated items constant.
Change-Id: I93b87cf854c3d6e2f33ef73ef25ffb3456ec27f4
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Merge the separate but very similar looking popTransition(),
pushTransition(), and replaceTransition() methods to a single
startTransition() method, and pass the necessary arguments in
a QQuickStackTransition structure. This is an enabler step for
being able to specify the desired transition type for replace
(and push & pop, for that matter) operations.
Change-Id: Ia68bb94dc9280aace8718f4df0e798a7f1469e78
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|