| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
Change-Id: If797ac58344b20e8de4379343131c097247ba2f2
|
| |
| |
| |
| |
| | |
Change-Id: If68cff4efacc7dc5719c8b8e61937e85e9076870
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The internal QQuickPlaceholderText creates an "implicit binding"
to the editor's horizontalAlignment, meaning that the placeholder
respects the editor's horizontal alignment when explicitly set,
and otherwise determines the alignment from the placeholder text's
visual direction.
[ChangeLog][Controls][TextField] Fixed the horizontal alignment
of the placeholder text in right-to-left UIs.
[ChangeLog][Controls][TextArea] Fixed the horizontal alignment
of the placeholder text in right-to-left UIs.
Task-number: QTBUG-55999
Change-Id: If1a8596c35c1920874996277520f1c54430c5f69
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
[ChangeLog][Controls][ScrollBar] Added snapMode property incremental
or discrete scrolling.
Task-number: QTBUG-56569
Change-Id: Id0d463b85063a62b7df6307af8fe8b203155a5de
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Before, the implicit size of TabBar was calculated based on the content
size of the ListView that TabBar uses internally. The problem was that
ListView calculates the content size based on the explicit size of the
items. There was a circular dependency, because TabBar resized the tabs
to the size of the view. To avoid the circular dependency, TabBar now
calculates the content size based on the total implicit size of the
tabs. As before, explicit size is respected for tabs that have it set.
[ChangeLog][Controls][TabBar] Added contentWidth and contentHeight
properties that are automatically calculated based on the total size
of the tab items, but can be manually overridden if desired. This fixes
an issue that TabBar was not able to reliably calculate an implicit
size, and could in certain scenarios enter an infinite loop due to a
circular dependency between the items' sizes and the tabbar's size.
Task-number: QTBUG-57858
Change-Id: Ie303cbc54247e87b0affc6bf32c7bf99acea4571
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|\|
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
examples/quickcontrols2/quickcontrols2.pro
Change-Id: If2f5e40487ba6515ba322f92380573727bdd6bc0
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
QQuickMenu had itemChildAdded() copied from QQuickContainer, but it
did not actually install an item change listener on the content item
so itemChildAdded() got never called.
Change-Id: Idfe558c7055b9a3df124b1f009941c423ecef4bb
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In comparison to handling synthesized mouse events, handling touch
events has the advantage that it gives multi-touch support. That is,
it is possible to move multiple dials at the same time, each handling
its own touch point.
Change-Id: Icabd971147f291fa4df00c6215c847d7976fda5f
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This makes it possible to interact with both handles and multiple
sliders at the same time.
Change-Id: Iba47b8ec31619b3dbec09dbc9ea176735f984e8b
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In comparison to handling synthesized mouse events, handling touch
events has the advantage that it gives multi-touch support. That is,
it is possible to move multiple sliders at the same time, each
handling its own touch point.
Change-Id: I713307b0e6b5ee777496fc9ba68a5180d13a6aca
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
[ChangeLog][Controls][DelayButton] Added DelayButton.
Change-Id: I94820dfb41ba9b90f0a29cda01ac476b54cf3de8
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function.
Change-Id: I3b7a07c7d0c0f9d95dfa312c3d1e398fcbaa304d
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The "rebound" name originates from Flickable::rebound, but for swipe
delegate the transition is not only applied on release, but also when
calling swipe.open() or swipe.close(). Therefore the "rebound" name
feels a bit off in this context.
Furthermore, this patch adds the missing docs and a changelog entry.
[ChangeLog][Controls][SwipeDelegate] Added a swipe.transition
property that holds the transition that is applied when a swipe
is released, or swipe.open() or swipe.close() is called.
Change-Id: Ic38ec850c64dd21b8d9deb08609172c6cb0f6d71
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: If25a058a6855e747ef3b5f253f486188593493a9
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
I missed it in fa766648b234c65b9025ad62f3a29eb83d89ae8f.
Change-Id: If3ba0700c1547fbc7af3671b5eeb364055880175
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I3869a87dc6efceb629772ed943aee11dfa25a364
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Iac4d5ad149111bdc5ac5b56bf246424b6f943bce
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
|\|
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/imports/controls/material/DialogButtonBox.qml
src/imports/controls/universal/DialogButtonBox.qml
Change-Id: I16cbf9912a3526783c21a6f30996f83fce9e02c3
|
| |
| |
| |
| |
| |
| | |
Task-number: QTBUG-57256
Change-Id: I4317242f48f7c94a35d3f0c9a6793ef113b69e77
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
It doesn’t make sense to do this.
Task-number: QTBUG-57266
Change-Id: I23f740356f2727a59aa0a68cb57d2c44edfb6046
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I53624e9cb23af49c37966d3e55d5b07f5a5edf47
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Ia0030b9ea7228dad242e29a439e3859dc0846229
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Ieab1117c3d674634c4431cd5eacd7686efbd14b2
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I68458505afaa528fbe2ed3d1ea488baba311234d
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I537581612f279e527a0304800bbe153b372e5c12
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I9907dbc49607a39452a18c5ad68c8acc8748b9da
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I4e73e5a1691dc6c68e4e1c8c4e8c53ae9dfb829d
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I6b1b8ea3872d5a4fc00f9786e29d3b7fa433bd11
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I58b1796152d72cf5f16ac4aa80eeeb133fde4c75
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I6d9d4fd85331777b6d29e25c6f25e0ced9662427
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Id41f6c68be54d16fab3cf83a9bbb462700bc8156
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I65bba3a7ed3ee43756450fef17da6be6219afd70
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Ie6e050fdd77b1711350ecc00f05d2e6bcd979fc5
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function.
Change-Id: Ia486e46339068a3767910a4ba8c249a39e58d8ed
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I5ef93db270196b8d2c367cdf74f82391331757c7
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Id164652edf88a487b6eb630768144e4a23650658
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Ie0123b8dead53967a080cceef144bba15ece19e1
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Iebec81dd54a8f6b0bde8a3ce10f99322d012cae1
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Ie553a2603236585f970f8513f1697de2f5d41ba1
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I7326cf69b4998cb12ab8ea0a946419ac85a55d31
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Ia0b8bb7e27a3bd1a1af863d1b56a89e089c5663f
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I1c032460f64c1ea09c0b4eebc0b29deec0a43e45
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Ife9d9680dcce6685c43e7ee52cd4782bc6961a3f
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I7f61bb8da4b89af8fd3e5f508fe1a683484e799f
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I5da1e875099cd134a69ac5f6d2593d930e0702b5
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I35f93fe3777ddaa2eca3239b4eb28030cf3dfe3b
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Ia0ae26235b8e466b80dd674a3d1f530795ade165
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: I1a90f1132c50abf2f2e6c978aa9248fbb385a71b
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Idb91be7036984e752134f85858eae2cd90cec462
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the appropriate objects are destroyed at the end of
each test function, even if the test fails.
Change-Id: Idcd59bfd851b307fdb9621f01ad90c41523d6049
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
|