| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
MenuItem provides signal onTriggered().
Change-Id: Id61aee07d0463bc66a9e50d931a791fc4e0783c2
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
| |
ComboBox::editable was added in Qt Quick Controls 2.2 in Qt 5.9.
Change-Id: I5db1a6448a23d0e4f539f11c074270670b83899f
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
It turns out that cancelling the incubation of eg. a combobox popup
alone is not enough when its children might be incubating and would
be left incorrectly guarded. Cancel recursively the whole object
tree of a replaced/destroyed delegate to avoid that.
Task-number: QTBUG-50992
Change-Id: Ia06931c4c7af3ed8bb56af6c29eb51081c4fccbb
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The initial drag threshold is a necessary evil on touch to avoid
conflicting with flickables, but leads to bad experience (QTBUG-47081)
when using a mouse. Now that we have separate mouse and touch handling,
we can apply immediate moves when using a mouse, but keep the old
behavior on touch.
[ChangeLog][Important Behavior Changes] ScrollBar now reacts
immediately when using a mouse.
Task-number: QTBUG-58667
Change-Id: I51759fc01dc8b8536834a8a3cca635ff512f7dc9
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
| |
Change-Id: I0521eb36ee01abc72edc869d92910e823f00a2f2
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test is sharing (and showing, and resizing) the same view for
every snippet. In the CI system we keep having issues that sometimes,
after running the test for a while, the window content stops being
resized as appropriate. Considering that QQuickWindow resizes its
content item in resizeEvent(), this probably means that in the CI
the window does sometimes not receive the resize event as appropriate.
Before, the window was left hanging there after taking the very first
screenshot. Now we try to close the window so that each and every
screenshot snippet gets loaded while the window is hidden, shows it,
and waits for it to become visible/active. This will hopefully ensure
that the window will always receive an "initial" resize event.
Task-number: QTBUG-58606
Change-Id: If4b38443cfdc9175f313bf8e70c7daf42d34f687
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
| |
Change-Id: Ie7ad814b3999791801c60776777c6a736db1c093
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
| |
Menus, dialogs, and drawers already handle it out of the box,
but for page/stack navigation we need an explicit shortcut.
Change-Id: Iad3e05f0fc31dbd66e3b1aa9286f8ef076fcff0d
Task-number: QTBUG-58105
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
| |
Missed in 24acfcaf.
Change-Id: I11c87a21d7d29befec5784eff1961a6feb5ea24b
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
| |
Change-Id: Ib7eb50df859ea598aac806dbd44f150f2b77e4e1
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The initial drag threshold is a necessary evil on touch to avoid
conflicting with flickables, but leads to bad experience (QTBUG-47081)
when using a mouse. Now that we have separate mouse and touch handling,
we can apply immediate moves when using a mouse, but keep the old
behavior on touch.
Task-number: QTBUG-59920
Change-Id: Ida36eed1f59a30173e3a2c53b55e044a87c98d8b
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The initial drag threshold is a necessary evil on touch to avoid
conflicting with flickables, but leads to bad experience (QTBUG-47081)
when using a mouse. Now that we have separate mouse and touch handling,
we can apply immediate moves when using a mouse, but keep the old
behavior on touch.
Task-number: QTBUG-59920
Change-Id: I097cbdaed4933c0d907097b75f15ba16dcf615b1
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The initial drag threshold is a necessary evil on touch to avoid
conflicting with flickables, but leads to bad experience (QTBUG-47081)
when using a mouse. Now that we have separate mouse and touch handling,
we can apply immediate moves when using a mouse, but keep the old
behavior on touch.
Changing the behavior is simple, but auto tests need quite many tweaks
so RangeSlider and Dial will be done separate follow up changes.
[ChangeLog][Important Behavior Changes] Sliders and Dials now react
immediately when using a mouse. Now the initial drag threshold applies
only on touch, to avoid conflicting with flickables.
Task-number: QTBUG-59920
Change-Id: Ifc1e6ed74c7894c3c854c975dff5238278827590
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
| |
Change-Id: I9c3f7997a14bd1824663c7521061c4ee43d6380e
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
For example, if you have a floating button on top of a text editor,
hovering the button must change the cursor from the editor's ibeam
cursor to an arrow cursor. This applies to all interactive controls
that call setAcceptedMouseButtons(). If a control blocks mouse events,
it should not use some random cursor from another control underneath.
Task-number: QTBUG-59629
Change-Id: I8a6ae306bbc76a9b22377361cb19cf9c3a872d31
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
This test was added in 88a62b3 that fixed the scrollbar cursor. It was
not possible to test in QML, so a separate C++ test was added. It was
noticed that most interactive controls have the exact same issue, so we
want to utilize the same test for testing the cursors of all relevant
controls.
Change-Id: I7c307de9f72760b0993007246beb3357a1b5ec2b
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
test_down() needs to place the popup below the combobox button to be
able to test its pressed and down states while the popup is open. On
some high DPI displays (Chromebook Pixel) the popup did not fit fully
below, but got pushed partly over the button. Consequently, mouse
presses went to the popup instead of the button and the test failed.
Change-Id: I03e5768e00cf1eaf6d704a16ffe2b8d1705021b2
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
| |
Task-number: QTBUG-59309
Change-Id: I3c19d55431dd4831c4510acb5ef0e9fffa8f478f
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
| |
Scrollbar over TextArea had Qt::IBeamCursor, although the textarea would not be activated when clicked.
Task-number: QTBUG-59629
Change-Id: Ie96ba03360fcfb5872f5bb6345e168c987978aca
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
|
| |
Random values of the m_elapsed could make the time in updateCurrentTime invalid.
Task-number: QTBUG-59911
Change-Id: I8d36f50f01679f56300df9bae00a8d5de6528cc3
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
| |
The signal was added in Qt Quick 2.9 and has revision 9.
Change-Id: Id1bb0f17ac5d8c9684ab5127782d030b54756e6f
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
| |
The signals have been there since the first release. The docs were
just missing.
Change-Id: I5f5340859136b8924832da4ddb2a18d4a812cca3
Task-numer: QTBUG-59400
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
| |
To use the same "was introduced in Qt 5.7" phrasing already used at the
top of the page.
Change-Id: I3736a1c3e87aa91e7fa3b8a41370f4b2252e793d
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
| |
To make it more clear what the controls are and how they look.
Change-Id: I6ce9a56a1692d90900952be798d7b254bc067dbb
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
The version table added in c9cd624 looked fine in locally generated
docs, but it seems to get a bit too wide in the online snapshots (the
table becomes horizontally scrollable). => Merge the controls and
styles columns that all have the same version.
Change-Id: Icb8387f95211ddee030cb410594adc9a6fad5c97
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
| |
This was mentioned in the detailed description of DialogButtonBox,
but could easily be missed by users looking at Dialog's standardButtons
documentation, because that doesn't mention DialogButtonBox.
Change-Id: If3229589e24992d3071388a044246906e739a918
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
|
| |
qtquickcontrols2-customize.qdoc:28: Can't link to 'Creating Qt Quick Projects'
qtquickcontrols2-customize.qdoc:28: warning: Can't link to 'Creating C++ Classes'
Change-Id: I5ddc57215fd65fa6a80819ee694b5e031676f5a7
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
| |
The property was added in 4a97498.
Change-Id: I0f21f499e74450780db85d5c2c92aa4a0367c3b5
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
| |
Change-Id: I5bce83d66615f11588988947d088d4b6ce5240b2
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
Separate the icon and its background to make the background stylable
and to provide the icons in high DPI versions later. Some icon files
have been renamed to match the sub-app name. When this example reaches
dev, we can use the built-in icon support with named icons.
Change-Id: Id87d1a001476194eb7e803802c90e7089f92b3b1
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
Don't show the window until we start taking the screenshots and
actually need a visible window.
Task-number: QTBUG-58606
Change-Id: I2fcab3b54f0faf67588a21e0732d2e6dbcee9194
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
|
|
|
|
|
|
| |
The Window attached property has not been used since 3bbd90c7.
Change-Id: I09e0c620aa83533c98316f50d6bfe3fd292761d4
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
| |
Native text rendering was removed in 3f5a66eb at the same time
SwipeDelegate was being developed.
Change-Id: I14eb1f335963abb9ead9450d62262990a3abc7d9
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
The demo was originally written to become a Qt Quick demo. Focus
on the QQC2 specifics now that it became a QQC2 demo instead. There
were also some outdated references after being refactored a bit
after the initial submission.
Change-Id: I96ef3f4745a295b2d8ab12a30fcbdf41a2c50626
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
Dial::valueAt() does not exist.
qquickdial.cpp:515: warning: Can't link to 'valueAt()'
The broken see also link was accidentally copied from Slider.
Change-Id: I781b7d0bcf15d3b34dd2b8784a273d5cd7218469
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
| |
To avoid crashes in the future.
Task-number: QTBUG-59532
Change-Id: Ie81f95939fc5655567f9d987cf040daf3a32df43
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
|
|
| |
Check for valid URLs and test object types. Throw warnings when
appropriate instead of crashing later.
Task-number: QTBUG-59634
Change-Id: Ia269dc8afd31b618f1ff7aec94d684029cb78244
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
| |
Store the current operation name internally to allow throwing
informative warnings when component creation fails.
Task-number: QTBUG-59634
Change-Id: I7506c5eb4be35878c8abd73a637357e0d8ae08a2
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
Previously it just dumped the error from the component, without telling
that it was anyhow related to StackView. Now it uses the standard QML
warning syntax and includes the name of the operation (push/replace).
Task-number: QTBUG-59634
Change-Id: Iea8df51f587c243ca065627e59bb0e5b5b526664
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
| |
This fixes a crash in QQuickSwipeDelegatePriavte's destructor when
using QML debugging.
Task-number: QTBUG-59532
Change-Id: I55f97039eb723652fec24e4c3a8ce5d1a8fb6c41
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
|
|
| |
Task-number: QTBUG-59661
Change-Id: I35627bafc57266cb7b2842fe02765536ca7eecba
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
| |
The documentation body was clearly copied from Control::font. Locale
doesn't have mutable properties. Instead, one has to create a locale
using Qt.locale(). Change the wording to match that.
Change-Id: I637b00808c29c16ee768820be327e3c780cfee64
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
| |
Change-Id: I799eb73a05842b1990b5615fd01ad5204c554f20
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If QQuickComboBox was destroyed while its popup was open, it emitted
highlightedIndexChanged() during the destruction due to the popup's
visibility change. Use setPopup(nullptr) to destroy the popup in a
controlled manner, that is, disconnecting the relevant signals first.
This way deleting the popup doesn't have weird side-effects during
the destruction of QQuickComboBox.
Task-number: QTBUG-57650
Change-Id: I1c55707be68a24e115276ffb6dfa1c89051a45ea
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
| |
It looks like af9536deeaf1123aaae5ce78cee7b4014a01d595 (in declarative)
changed the format of warning messages.
Task-number: QTBUG-59536
Change-Id: I9a8228448ef136f65258b985c3dddf011063c49c
Reviewed-by: Liang Qi <liang.qi@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 6a5e030fbfa5f2adeabc6284f6ae3993e3d658c7.
The qt5.git integration went through, so this can be reverted now to
make way for a proper fix.
Change-Id: I73f9aef29683172360e85026e1c8c93b8409eeae
Reviewed-by: Liang Qi <liang.qi@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
qmlRegisterRevision() registers a nameless type, so using it would make
AbstractButton throw confusingly formatted warnings:
QML : <warning>
instead of
QML AbstractButton: <warning>
Change-Id: I6b51824ad019ed9451079cf8a2595e908ef8187e
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
| |
This is needed in order for af9536deeaf1123aaae5ce78cee7b4014a01d595 to
be integrated into qt5.git.
Task-number: QTBUG-59536
Change-Id: Ie1405a498018473029ce34de7dd95189aa75f203
Reviewed-by: Liang Qi <liang.qi@qt.io>
|
|
|
|
|
| |
Change-Id: Ie371dced41ed86373aeb0a4600cb0245b4550b7e
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|
|
|
|
| |
Change-Id: I0352376201a1efd318f89a758dd8dc5a269742f4
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|