| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes: QTBUG-77909
Change-Id: I87d41ab973ec5cb8a9cebcf0f22065e1bac221d8
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|\ \ \ |
|
|/| | |
| |/ /
| | |
| | | |
Change-Id: I629cb2b733de2e5533d8ba9f1665d14f542979b9
|
| |\ \ |
|
| |/| |
| | |/
| | |
| | | |
Change-Id: Ib1c507845cae7f354fe5a5fb9d71ee6963949bd0
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the x/y position of background depends on the height/width of
background and these values are not constant, the if statement in
the method resizeBackground() will always pass. And since a change
listener is set before calling setHeight()/setWidth() in background,
these two method will always call resizeBackground() and then call
themself recursively, that means the height/width of background will
always be reset, no matter what value you set.
[ChangeLog][QtQuick][QQuickTextArea] defer adding change listener and
prevent changing size of background recursively in construction
Fixes: QTBUG-76369
Change-Id: I2ec37cad7f35cb1c756276326fe69e860c6b8de5
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|\ \ \ |
|
|/| | |
| |/ /
| | |
| | | |
Change-Id: Ic804e1279f39b1bc09f9d45b2b3415067854ec09
|
| |\ \ |
|
| |/| |
| | |/
| | |
| | | |
Change-Id: I8c038d287f066f2935ba0bceef5dd078704fd276
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These tests where failing sometimes in our CI, because centerOnScreen()
was invoked which asks the window manager to move the window, but does
not wait for the event's completion. The solution is to do all that
*before* the initial qWaitForWindowActive().
Fixes: QTBUG-73128
Change-Id: I06c1f85d5ff9657dccab50f29084f7624cd7e194
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: I9100d20b76b9cc6ac138f474e5d808db19ed6684
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Reasons:
1) Qt::TexturePattern has never set by any code (this branch is
unreachable);
2) There is no knowleage about any brushes in QML (this method is
supposed to be invoked from QML only). Palette is used for colors only;
3) Even if brush style has been set somehow, it will be erased during
palettes resolving process after assigning a new "window color".
Looks like this code was copied from widgets styling and has been
compiling only because of the current design. In light of redesigning
palette class this code also makes no sense. Bringing knowledge about
brushes and its styles to QML requires additional job.
Change-Id: I555d062335593ad945b024136750dcd548cd9f16
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Reviewed-by: Nils Jeisecke <nils.jeisecke@saltation.com>
|
|\ \ \ |
|
|/| | |
| |/ /
| | |
| | | |
Change-Id: I76bfa11f39261e03b52ad237a09ff623bc865e0f
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
[ChangeLog][QtQuick][QQuickComboBox] countChanged signal now will be
emitted when a new model is set to the ComboBox
Fixes: QTBUG-75972
Change-Id: Ic26718453ba06ba284ac5903fc6f55ddf3523331
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Task-number: QTBUG-74391
Change-Id: I354049c5c8edb36cb94afa4483ae177a736f2374
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The QChar ctors from integral non-char types are under
consideration for adding explicit.
Fix users of these ctors ahead of the change.
Change-Id: I2d8f5276fe448ac2a3b3332e1b3773556ef9c676
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: I1e76b546c54b1fe58b4094bcb96a3692c2242d2e
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
|
|\ \ \ |
|
|/| | |
| |/ /
| | |
| | |
| | |
| | |
| | | |
Conflicts:
.qmake.conf
Change-Id: Ib55ecb95e5ae47cc7a46f136a2f2eb158676ea34
|
| |\ \ |
|
| |/| |
| | |/
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
.qmake.conf
tests/auto/accessibility/tst_accessibility.cpp
Change-Id: I0bc187e2a8edb4e357c1bf114dd9b1977d5c1e45
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The count variable should be updated after removing the item.
Fixes: QTBUG-76164
Change-Id: I141d720ffaa890002d98a7d2448adca9a7d7d2f3
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| | |
| | |
| | |
| | | |
Change-Id: I3d0cfbbd68b361f006a455e46e17e0da28823373
|
| | |
| | |
| | |
| | |
| | |
| | | |
Change-Id: If4f3dca99638015b479509e4aa73e0190b1182ac
Task-number: QTBUG-67343
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Task-number: QTBUG-75558
Change-Id: Ic9856c6f6da4e0beefe2fe6f1bbaea8fdd67ea0d
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Task-number: QTBUG-75546
Change-Id: I6e672c3a8390c4cf10dc9576cc3bf1eb10a6246b
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
|
| | |\ |
|
| | | |\
| | | | |
| | | | |
| | | | | |
Change-Id: I589b709ab12bb2b55596079f53ef147a82f23a3e
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I2389ce274d609c13055e82408f38d30c6e921e5c
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: If3c56e80803135ac7e1ce99033da8e3dd09ad7a9
|
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
To make switch work, the base class now returns checkbox when it has the
checkable property. With that change, this is no longer needed.
Change-Id: I41d8f774cb244f922b859fd9f2dde75913e965b6
Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes: QTBUG-76356
Change-Id: I8f8e8331adbe741be2c893f2140d793d1b901434
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- The correct module header name is QtQuickControls2
- Add dependency to qtgraphicaleffetcs
- RangeSlider: Move \qmlsignal commands out of \qmlpropertygroup
- Fix linking to content[Width|Height] for ScrollView
Change-Id: I1636fef5f4365a8e9f80b0b8df17e78999bfd3f8
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
According to https://material.io/design/components/buttons.html#text-button
Change-Id: Ia36a676864a8f738d204cf8db9430b797f1f2f99
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: Ib83e2ec925e0c37b40562aea7f11e09759ce3abc
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Otherwise we cannot interpret them as the original key sequence anymore.
When passing them on they are interpreted as the number key that
represents the numeric value of the key sequence enum.
Change-Id: Idd94ef95bc693cb6d51162dd1994adc953b52e25
Fixes: QTBUG-75572
Reviewed-by: Henning Gründl <henning.gruendl@qt.io>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The cursor flash iterval can sometimes be set to 0. This is done
from e.g the iOS plugin while selecting text, since the
cursor should not flash when the user is dragging it around
inside a magnifier glass. Setting the interval to 0 simply
means "don't flash", rather than "hide the cursor". But
setting the interval of a QML Timer to 0 will cause it to
never trigger, which is not what we want, since then the
cursor can end up staying hidden if done in-between two
"flashes".
This patch will add an extra condition that checks for this case.
Fixes: QTBUG-75844
Change-Id: Ib1ca594a49a18cb161a2b2a67928fb6766984988
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of casting to int and back to enum, just use the enum directly.
Change-Id: Ifbd6a74ee499ffaeb99b0b4274cd59365833bfbd
Reviewed-by: Liang Qi <liang.qi@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Current behavior is to always decrement the currentIndex when the current item
is removed -- even when the current item is item 0. This means, for example,
that in a TabBar with three tabs and the first tab selected closing the first
tab will leave nothing at all selected.
Change behavior to keep currentIndex at 0 if there are still items left in the
container. Now closing the first tab will leave the next remaining tab selected.
Change-Id: If4e1903366e29fcee8226b776d5b2e03cec189df
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The important part of the "cascading" test is checking that the sub-sub
menu eventually opens, so move the !visible check to the non-cascading
branch of the if statement.
Change-Id: I5a09bf0b5d45832f7b75c3e8c397fdb9e6fcc011
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>
|
| | |
| | |
| | |
| | | |
Change-Id: I838d61be2f84240b3aaf3b9658a0e0e337313470
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
BC file added.
Change-Id: I7aca8182bb24e0064d8b76e71ad7353a4988c2f7
Reviewed-by: Sergio Ahumada <sahumada@texla.cl>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A result of qtdeclarative d4d197d06279f9257647628f7e1ccc9ec763a6bb.
Following similar change in qttools 875a927b49b241e6a96f2c8aace8a9c69da04ce7.
Change-Id: I0f11dbf09ffa3aeb7395e7a8eb6a38bcc5f60133
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These tests have not failed on the removed platforms for at least 60 days
Task-number: QTBUG-76608
Change-Id: I0f49529cc567fcc8eaffbe06adb4b260cd1a9e06
Reviewed-by: Frederik Gladhorn <frederik.gladhorn@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Task-number: QTBUG-76491
Change-Id: I2d141866c13046abaaa7eead1989372fa9fbc5de
Reviewed-by: Marc Mutz <marc.mutz@kdab.com>
|
|\ \ \ |
|
|/| | |
| |/ /
| | |
| | | |
Change-Id: I969e9957826a0e74650ae31b10cf8ca550f32891
|
| |\ \ |
|