| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I323f708c857366c0b50d143d67b96bee3f7a1a98
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Ia0b95ed25cad55477d90038db39ac22a6a3932ed
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes it more convenient to create a bunch of checkable buttons
where one is checked:
Column {
Button { checked: true }
Button { checkable: true }
Button { checkable: true }
}
Change-Id: I797d0d08256a4006194bc8db0ddfe4d2c7902d85
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Ia28054f5860bf65c87a0c8cfcc09f7c9a769c7cf
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Made Switch indicator and handle smaller to be more like the native
switch on Android. Also, increased the sizes of Switch and its Ripple
CheckBox, and RadioButton to to correspond minimum touch target size
48x48.
Change-Id: Icce70215910b677d989182fbb3b40161033601f8
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
Reviewed-by: Nikita Krupenko <krnekit@gmail.com>
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I5aec1c2a08b24e1779e62b9580a740fb102c1561
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I6ba9d1c41b2ab6766faef6cdbdfb780e6ca37dfd
Reviewed-by: Liang Qi <liang.qi@theqtcompany.com>
|
|
|
|
|
|
|
| |
Only one is used. Cleanup the API a bit by merging the two.
Change-Id: I90d72e754442aef45e9d1bc3f86004cad511a726
Reviewed-by: Liang Qi <liang.qi@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For some reason this crashes:
ScrollIndicator.vertical: ScrollIndicator { }
But using the attached property via template works:
T.ScrollIndicator.vertical: ScrollIndicator { }
Good enough solution for now. :)
Change-Id: I7a631a66ad24b1ddf7852c7c11d3850e49a52c9b
Task-number: QTBUG-50757
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Calling QJSEngine::evaluate() is a heavy operation. Only one of them,
namely textFromValue, is used from QML, so there's a good chance that
valueFromText doesn't need to be evaluated at component creation time.
This change postpones the initial evaluation to the point where either
callback is requested.
Before:
RESULT : tst_CreationTime::controls():"SpinBox":
0.53 msecs per iteration (total: 68, iterations: 128)
After:
RESULT : tst_CreationTime::controls():"SpinBox":
0.39 msecs per iteration (total: 51, iterations: 128)
Change-Id: I1730dc4024d0a556ca2da765ac3c52ba8a29f743
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
|
|
| |
Remove the explicit font size leftover, and tweak the implicit size
bindings so that neither tst_accessibility nor tst_snippets throws
any binding loop warnings.
Change-Id: Ib60dc8a1fca33b14171320db3f37e65c046f5898
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Ibbc6dda27172425250e0543817b4ab5b303bded5
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
| |
Change-Id: I240b4bb7d59f806584d89c93560cc0da39a77d56
Task-number: QTBUG-50712
Reviewed-by: Liang Qi <liang.qi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I423c78ab33f78032471db64804885ba60671d93b
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Even though I didn't want to expose this, because I'm still hoping we
could make QQuickPopup inherit QQuickControl in the future, the fact
that QQuickPopupPrivate::get(popup)->popupItem was used in so many
places is a good indicator that accessing the popup item is often
required when dealing with popups. In any case, this is C++ only API
and not exposed to QML, so it's not that big deal... and we can
always deprecate it later and make it return "this" should the item
plans come true.
Change-Id: I6b99a499327d838ee61eae70f8ebf8e77f00ae39
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I5a8a231be3fed56185066dd9d939d1b898083a68
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
| |
The red color is one of the secondary colors listed at brand.qt.io.
Change-Id: Iea8afe0afe06ea033cb0ece864b6049d74765dfa
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
| |
On my Linux box, the creation time of ComboBox { model: 100 } goes
down from ~4ms to 0.9ms.
Change-Id: I8c3d8233d961c0b895581ba347d6789063a587a3
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I75d21043ab61186fc8156011e03b163c72d19114
Reviewed-by: Liang Qi <liang.qi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I6927ee293e5126abc037a3eb9f86a67825732679
Reviewed-by: Liang Qi <liang.qi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I29e286b9df08fc531f053158da379c5d6898bada
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
|
| |
If we ever want to expose these, the name would be something else
than "mouse"... :)
Change-Id: Ie9dad16e84708059fd0b43d4764925db7b014d64
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The indicator is now a single QQuickItem, and runs in the render
thread, so keeps animating even if the app is busy.
Before:
RESULT : tst_CreationTime::material():"ProgressBar":
0.30 msecs per iteration (total: 79, iterations: 256)
After:
RESULT : tst_CreationTime::material():"ProgressBar":
0.18 msecs per iteration (total: 93, iterations: 512)
Change-Id: I3ec0982da9a02751725692c72da10a01d2afbfdc
Task-number: QTBUG-50161
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I3e09c4e2b6cbbe39bdf9e943905664e5dc1fe954
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Ie3d0f50a59aeaab36ec388af897cbf2596269ce3
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
| |
Add a manual test similar to that in Qt Quick Controls.
Change-Id: Ic93026f3b1333613be43b8827ddf3702c2ef5b70
Reviewed-by: Alessandro Portale <alessandro.portale@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Iafc571cc2b18a0c68d0cf7fca6d6775062f710f1
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Other styles don't have padding either. No padding makes it possible to
put a ProgressBar at the bottom of a ToolBar or other AppWindow header,
which is common in mobile apps these days.
ApplicationWindow {
visible: true
header: ToolBar {
ProgressBar {
value: 0.5
width: parent.width
anchors.bottom: parent.bottom
background.visible: false
}
}
}
}
Change-Id: Ia43c5bfd0b58dafd5ff0ad4c65fa95f156622aa4
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
| |
Change-Id: Ia43ba18cfd7ce9f5c4c28e239645320af5ba41e7
Task-number: QTBUG-50141
Reviewed-by: Liang Qi <liang.qi@theqtcompany.com>
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
|
| |
We don't have a design yet, so this is just something improvised based
on the old flat style tab design & adapted to default style colors.
Change-Id: Icd08d32bb08a97ac4cba21a647dbd5b043cb7c91
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: If2ddb2c65fec2a0159d740c788b7f21c1c7f0637
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
|
| |
QTBUG-49979 was fixed, so we can switch back to using layer.effect,
which typically leads to one less item and much less bindings.
Change-Id: I7d1d1462a90c674b5f849134bb6ac8fe6ff0f231
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Iabd0235753414107c1db6d0d1354f944301d04c9
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
| |
Change-Id: I39f6edac0cbea3a5ac9aae7fe65f61e19cbaa7a1
Task-number: QTBUG-50471
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The result of:
Frame {
ColumnLayout {
RadioButton { text: "First" }
RadioButton { text: "Second" }
RadioButton { text: "Third" }
}
}
is now identical to:
Frame {
contentItem: ColumnLayout {
RadioButton { text: "First" }
RadioButton { text: "Second" }
RadioButton { text: "Third" }
}
}
Change-Id: I823b2259dabb66db0dddef41ea396f7ac1000a82
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I26a8ae03e57df79fa87e26c3b650a49f2b89aeac
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I4a52468234f0479c1b8feb102e07686e3235ba3f
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows nice bindings such as:
Slider {
id: slider
Popup {
y: -height - 1
x: -width / 2 + slider.handle.width / 2
parent: slider.handle
visible: slider.pressed // <---
Label {
text: slider.position.toFixed(2)
}
}
}
Change-Id: Iebde004205636de31d0f0dd0f6404f0755aaf0df
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
| |
Same as 89e058, but for close(). If the popup is already closed, then
close() should be just a no-op.
Change-Id: Icf1a3c5f67aad9b76432608802aa345881f5b960
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I6642a740c93c24cc86b4c7377def252390ca9f71
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I68f25669379043bbe19b61428cd85dba7eb2ae70
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
| |
Behaves the same way than the Pane/Frame/GroupBox container controls.
Change-Id: I370f3961b77a363a63a0a64fc629cc5da6dfd53f
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
|
| |
If the popup doesn't fit on the screen, try flipping it around so
that a popup that is requested to be positioned below the parent
item is tried to fit above, and vice versa.
Change-Id: I59d3b5e5cb1a45f894122f0aff459efd5065e2e9
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The parent defaults to the QML parent object where Popup is declared.
Popup::x/y are relative to the parent, and the popup also automatically
follows the parent as appropriate. QQuickPopupPositioner has been
adapted from Qt Quick Controls 1. It was called QQuickScenePosListener,
and it was implemented for the text selection handle popups.
ComboBox's popup now follows the control eg. when scrolling, but the
below/above positioning feature is temporarily gone missing. It will
be restored in a follow up commit.
Change-Id: I8a6b58cd74e07f33930abc35d0ab9da056685128
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
| |
Change-Id: Ife8ec7e14f940068a809cdf7a715a1790cce3f66
Task-number: QTBUG-50305
Reviewed-by: Nikita Krupenko <krnekit@gmail.com>
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
|
|
| |
Popup accepts/blocks all input events by default, to avoid them leaking
throgh. Subclasses may override the event handlers to implement eg.
key navigation (menu).
Change-Id: I726b6a3f61a397e4f95d736c6617dd77a35b01dc
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I39b5a473f56ea05d26e9b28eef30364c9281d137
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Added relevant properties to make it almost like a Control: x, y,
width, height, padding, background... This change makes popup use
an internal item where the style/user-supplied contentItem and
background are re-parented. This way we can provide a default style
(background) for Popup.
Change-Id: I3e7933562464c5c852e4ba4bc37d9ac25691c714
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
|
|
|
|
| |
Works the same way than QQuickControl::contentItemChange(). This is
more efficient and correct (in theory, supports changing the content
item at run time) than connecting to the contentItemChanged() signal.
Change-Id: I09db809760ddf2c7d62cc2937a6b821f0cd4dad7
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Ib223ea2ef258fdc7812ed2daf329263e12292a52
Reviewed-by: Liang Qi <liang.qi@theqtcompany.com>
|