| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
Change-Id: I1c820dbd76414000a4e3d4f51ab85cf61bf33760
Reviewed-by: Akseli Salovaara <akseli.salovaara@qt.io>
|
| |
|
|
|
|
|
| |
Task-number: QTBUG-130067
Pick-to: 6.11
Change-Id: Id27b457908470ea419a8b811c6750ecf8bdfe55f
Reviewed-by: Doris Verria <doris.verria@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
For some reason, the QuickTools package is not implicitly included
when building for Android like it is on desktop platforms.
Pick-to: 6.11
Fixes: QTBUG-142665
Change-Id: Icdc5afab85ed6061f47e976d5189879b5d47c083
Reviewed-by: Eirik Aavitsland <eirik.aavitsland@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
Porting from the Qt5.
Pick-to: 6.11
Task-number: QTBUG-102301
Change-Id: Ic4aa3e4c3f759ccd6e04ef77ed5c2f888e7f9aa0
Reviewed-by: JiDe Zhang <zhangjide@uniontech.com>
Reviewed-by: Liang Qi <liang.qi@qt.io>
|
| |
|
|
|
|
|
|
| |
The Window type doesn't handle palette changes automatically.
Fixes: QTBUG-134767
Change-Id: I039f2bda7aeb1ba534c357bca30b1cfa693362a2
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the application wrote a new value to a property in the style, we
used to emit a property changed signal for that property from every
StyleKitReader (control) in the application. We did this because we
could not easily know which controls would be affected by such a write
because of property propagation. This could therefore be very slow.
But now that we have more functionallity in StyleKit available, such
as being able to resolve a controls base types, we can now improve on
this logic.
Therefore, this patch will ensure that we instead only emit changes
from the StyleKitReaders of the same type (or a base type) as the
control written to in the style. The result is that a write from the
app, such as:
StyleKit.style.groupBox.background.radius = value
will cause an update only for groupBoxes, skipping all other controls.
This is clearly faster.
Task-number: QTBUG-130067
Pick-to: 6.11
Change-Id: I6432db93f282b8155d9270a57206f0d558b801a8
Reviewed-by: Doris Verria <doris.verria@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As it stood, if you e.g did:
control.background.shadow.visible: true
control.hovered.background.shadow.visible: false
Then the shadow would stay visible also when the control
was hovered. The reason was because the shadow was already
created in the normal state, and toggling visiblity after
that point had no effect.
This patch will fix this, so that we hide the shadow if
its visibility is set to false after first having been
created. We refrain from destroying it again, since doing so
has a higher cost, and most likely, the hiding of
the shadow is just temporarily.
Task-number: QTBUG-130067
Pick-to: 6.11
Change-Id: Ib107b11b7f7fa638d7ac439348b9ccb75bf1bb1a
Reviewed-by: Doris Verria <doris.verria@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
The Accessibility Insights for Windows requires focusable controls to
have a name. Ensure that those controls that don't get one by default,
also have a name.
Task-number: QTBUG-141669
Pick-to: 6.11 6.10 6.8
Change-Id: I6d19bffd24d7ac5b1b93fe4eaa003cefede09b13
Reviewed-by: Morten Johan Sørvig <morten.sorvig@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We used to bind several of the colors in the Fallback style
the palette. This turns out to be not such a good idea. The
reason is that the palette differs across platforms, which
means that a style created on e.g macOS can end up looking
completly different when running on Ubuntu.
While this might be wanted sometimes, more often it has the
potential to come as a surprise at a late stage during
development, and contributes to a "write once, debug everywhere"
scenario.
This patch will therefore change this. We now choose to follow
the Basic style approach, and "hard-code" the colors in the
Fallback style to be the same on all platforms. This gives
developers a stable platform to build their own styles on top
of.
It's still fully possible to bind all colors in their own
style to the palette, if they want a more dynamic style that
respects the platform palette.
Task-number: QTBUG-130067
Pick-to: 6.11
Change-Id: Ibeeedacb35b5a4c68c827b66baf0298a42b2948a
Reviewed-by: Doris Verria <doris.verria@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
The examples that demonstrate hybrid UI approaches lack proper
descriptions. This commit restructures and enhances the descriptions
for these.
Task-number: QTBUG-134102
Pick-to: 6.11 6.10
Change-Id: I5cf604fee932024cbe73347696e19f9c6e22d5b7
Reviewed-by: Alexei Cazacov <alexei.cazacov@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Q_{ENUM,FLAG} does what Q_{ENUMS,FLAGS} did plus declaring two friend
functions, so the behavior should be the same.
For enums that are declared as flags (with Q_DECLARE_FLAGS(Es, E)), use
Q_FLAG(Es) which will register each enum value with the meta-object
system.
Q_FLAGS usage in tests/auto/qml/qmlcppcodegen/data/enumproblems.h is
testing Q_FLAGS itself.
Q_ENUMS/Q_FLAGS have been deprecated since at least Qt 6.
Pick-to: 6.11 6.10 6.8 6.5
Change-Id: Id21b6e3205a786b3a5fa04bd09dfee2a6c1c2a86
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
| |
|
|
|
| |
Change-Id: I01bcdaea8a7014c3bd2f1c65b7d00a048700b91f
Reviewed-by: Doris Verria <doris.verria@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A Qt Quick Control will use StyleKitControl.text.color as its
text color. But as it stood, it was not initialized to anything
in the FallbackStyle. The result was that all controls got a black
text color, regardless of what was set in the theme palette. It
would also not respect any palette overrides done from the app.
This patch will make sure that we, by default, bind text.color
for the various control types to the matching color in the
Qt Quick Control's palette. This color will, unless overriden by
the app, be initialized to the color set by the theme.
Change-Id: I6d4f67c81c57c9a30940a720816fa4ed2675b8bd
Reviewed-by: Doris Verria <doris.verria@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
This patch will implement support for styling ScrollBar
and ScrollIndicator. It also includes ScrollView, since
otherwise, if we inherited the one from the Basic style,
it would also use the ScrollBars from the Basic style.
Change-Id: I8163824aec61ce3c84303b6add3fdb1b7701532e
Reviewed-by: Doris Verria <doris.verria@qt.io>
|
| |
|
|
|
| |
Change-Id: I8a7fc86482e2083a24d1e7159737fd0ababc8e0b
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
|
| |
|
|
|
| |
Change-Id: I0177d20c381d83d2a816199a89b6fc9150fa4766
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
|
| |
|
|
|
| |
Change-Id: I3594798dfb475118cad046948ccc4fe180bbd9a3
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
|
| |
|
|
|
|
|
|
| |
It's redundant as the class name is QQStyleKitPropertyFont.
Also this makes it consistent with the palette API.
Change-Id: Ic334c1febb1cdfb5cb09f898cb2f27ecb06c1c1f
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
|
| |
|
|
|
|
|
|
| |
[ChangeLog][Controls] Added DoubleSpinBox.
Fixes: QTBUG-67349
Change-Id: Icb2f02162825daf74778de725f80af63874a5d16
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
|
|
|
|
|
|
|
| |
This allows to override certain font properties per control/state. So
then the final font propagation logic becomes:
Fallback Style -> Style -> Theme -> Control -> State
Change-Id: Ifb451b156b0e4de7734ac7b31a002cd3fcb78dd0
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a fonts property to the style that allows you to set fonts per
control, similarily to what we do in QQuickTheme.
The fonts are propagated from the style to the theme, and from the
fallback style to the style. That means that if a font is not set
for a theme or style, it will be resolved against its fallback font.
Since both the QQStyleKitTheme and QQStyleKitStyle should have a
fonts property, introduce a common base class: QQStyleKitThemeProperties
that contains the fonts property. Later, the palettes can be moved
there as well.
Also add a font property to the QQStyleKitReader that is suposed to
return the font for the current control being read.
Change-Id: I116c1ab9bc426570756476ee409513587c475a0d
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch will add support for Instance Variations. Instance
Variations allows you to define one or more style variations in
a StyleKit style that can be activated from the application
using an attached 'StyleKitControl.variations' object.
Instance Variations will affects all descendant StyleKitReaders
of the item that contains the attached object.
For example, if you set "StyleKitControl.variations: ['mini']"
on a GroupBox, all controls inside that GroupBox will
be affected with the variation named "mini" in the style
(if any).
Inside a variation, you specify which controls should
receive alternative styling when the variation is applied.
Any properties defined in a Variation override those
set in the Style or Theme.
In order to support Instance Variations, this patch will also
refactor how we implement Type Variations, which are variations
that applies to _all_ controls of a specific type, rather
than to individual instances.
Change-Id: I6486979281997e69b65da0ed4866b264c91c592f
Reviewed-by: Doris Verria <doris.verria@qt.io>
|
| |
|
|
|
|
|
|
|
| |
This will match them with Q4A.
Task-number: QTBUG-138877
Pick-to: 6.10
Change-Id: Ia5cb1954b361f7f0abb788c326045f71da202607
Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
This patch will add a new example to Controls that demonstrates the
new StyleKit API that has recently been added to Qt.labs. It
contains a few styles that the user can choose between, where each
style has a different level of complexity.
Change-Id: Ie193105c05759eee2b4f4deb9d1932448d7e36c5
Reviewed-by: Doris Verria <doris.verria@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
Alternate text (alt text) improves the documentation experience for
screen readers and for other accessibility tools.
Pick-to: 6.9 6.10
Task-number: QTBUG-135120
Change-Id: I975c3de11f893882fb9a27218079f244bd38a622
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The qml-i18n example and the qtdeclarative repo itself depend
on the LinguistTools CMake package, which is not available while
building qtdeclarative.
This results in:
- missing build coverage for the example
- a cyclic dependency, because qtdeclarative depends on qttools
(because of LinguistTools), and qttools depends on qtdeclarative
(because of qdoc needs)
- we try to find a module that will never be available, unless
qtdeclarative is built together with qttools in a top-level build
- in certain cases, if the top-level build fails early enough, the
cyclic dependency causes reconfigurations to fail
Remove the example, the lookup of LinguistTools, and the linguist doc
references to avoid all these issues.
Replace the qt_add_translations reference in the docs of the
QQmlApplicationEngine class with a snippet copy.
Pick-to: 6.8 6.10
Task-number: QTBUG-141465
Change-Id: Id88603a3753f53dfac9f350e981073effda15eb1
Reviewed-by: Masoud Jami <masoud.jami@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Re-arrange and add section headers to adhere to the app template.
* Replace first-person plural (we) with either third-person singular
(the example) or second-person singular (you).
* Add qdoc links to C++ or QML entities.
Fixes: QTBUG-137898
Pick-to: 6.10 6.9 6.8
Change-Id: Ib61ca9beac1bafb4e4e5f8fcc6475093b313768e
Reviewed-by: Jerome Pasion <jerome.pasion@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Continues 2d44365f69b9bc946d085c6b149e2ac319700265 and
b7f448f8647a9a118cee2d79d446194b20d4b335
* Qt 6.0 enabled and encouraged users to import QML modules without
specifying a version number
* Qt 6.5 enabled and encouraged users to create QML modules without
specifying a version number
With this approach, there is little benefit in specifying
QT_QML_SOURCE_VERSIONS, especially in an example module that is not
consumed by external software. It does not need to worry about
compatibility/versioning.
Task-number: QTBUG-89033
Task-number: QTBUG-140406
Change-Id: I7f83dc7430180b79b70c75e7ce7b3aef46a028ae
Pick-to: 6.10 6.8
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
| |
|
|
|
|
|
|
| |
Using JS placeholders inside qsTr() is a bad practice, and makes
translations impossible
Change-Id: I08dffd1a718a7112a8e426a013419578ec2f16f0
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Add API for specifying individual corner radius values similar to Quick
Rectangle. Try to keep the overhead minimum when not used, by storing
data in lazily allocated extra and using separate shader.
Use the API in the neumorphicpanel example.
Task-number: QTBUG-141110
Change-Id: I90e558526dff01c88fb2d163a33704b8f73aa1fc
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the initial window width was so large that the inital layout was
determined to be the "largeLayout" (wider than 450 pixels), then the
binding
columns: Math.min(Math.round(width / 130), 6)
initially resulted in 0 columns because the width was initially
evaluated to be 0, which caused the grids implicitWidth to be 0 (because
it couldn't fit any items when columns was 0). Hence, it was
"deadlocked": it didn't add items because columns was 0, and it
didn't increase columns because it's width was 0.
An item in a layout with implicitWidth == 0 will always have lower
priority to grow than items with a larger implicitWidth - hence the grid
was stuck at width == 0
Pick-to: 6.10 6.8
Fixes: QTBUG-140533
Change-Id: I558463ac33db36fa7eb8df4c70adc94f90c69e8f
Reviewed-by: Santhosh Kumar <santhosh.kumar.selvaraj@qt.io>
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
|
| |
|
|
|
|
|
| |
Task-number: QTBUG-140916
Pick-to: 6.8 6.10
Change-Id: I7c3e50c277f28a9af9347fcf61e205187334be2f
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Let the CMake structure reflect the existing module structure while
making use of the auto-generated qmldir files. The qmake project and
Qt Design Studio project are unaffected as they continue using the
manually-written qmldir files.
Drive-by edits:
* Renamed the (unused) URI of top-level module to disambiguate it from
the module that contains the actual styling code:
"flatstyle" -> "FlatStyleApp"
* Updated the docs to talk about QML modules instead of plugins
Task-number: QTBUG-132922
Change-Id: I163a6c6a86a4eaf210a18433e6e5ea1f1fc67dd2
Pick-to: 6.10 6.8
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of only moving the demo indicator and header slightly
to the top when no page is selected or demo mode is inactive,
hide them altogether so thay they don't end up showing under
the system bars on Android.
Also, for flickable pages clip their content so they don't
end up scrolling to the top underneath the header and showing
partially below the system bars.
Pick-to: 6.10
Task-number: QTBUG-138022
Change-Id: I31da83ce5978dc1cab63cfe39d53f2d2c72088a9
Reviewed-by: Rami Potinkara <rami.potinkara@qt.io>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
|
|
|
|
|
| |
Fixes: QTBUG-140544
Pick-to: 6.10 6.10.0
Change-Id: I951d3bae73157ccf2cfcf549b506a44651719243
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Otherwise one gets errors like the following in standalone examples
build:
CMake Error at tools/svgtoqml/Qt6SvgToQmlMacros.cmake:65
(add_custom_command):
Error evaluating generator expression:
$
No target "Qt6::svgtoqml"
Because the examples now use the new qt_target_qml_from_svg()
function, which will try to reference a non-existent svgtoqml tool
target.
Change-Id: I16b10c4fa31bd73d0d95bbad371cde54f17c236a
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|
| |
|
|
|
|
|
|
|
| |
Use modern string literals and replace #if-defery by a check on
QOperatingSystemVersion::currentType().
Pick-to: 6.10 6.9
Change-Id: I319b6c7665a4c4cadd7d1e711d8527f79ca35261
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
Amends 9601b74dabed53e93a7a5144d4c1fadb7876db18
The example no longer runs with Qt 6.9 or older as it uses the new
(Horizontal|Vertical)HeaderViewDelegate types.
Change-Id: I8430f4e9a48ddc9f72b20a4e998fde21480c4032
Pick-to: 6.10.0 6.10
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-Updated QtQuickView and QtQuickViewContent links to new pages.
-Added links to QtQmlStatus Enum and QtQmlStatusChangeListener interface
classes.
-Removed the qdoc QtQuickView file.
-Updated links in examples and the main Qt Quick for Android page.
Task-number: QTBUG-127747
Fixes: QTBUG-138917
Fixes: QTBUG-123106
Fixes: QTBUG-135474
Pick-to: 6.10 6.10.0 6.9 6.8
Change-Id: I61a64c8637c222290e4c630d75d579f6bb23886c
Reviewed-by: Ville Voutilainen <ville.voutilainen@qt.io>
|
| |
|
|
|
|
|
|
|
| |
Note the expected fill rule, as defined by TrueType, and explain that
if the stroked outline looks bad, it's the font's fault.
Pick-to: 6.10
Change-Id: I8c4c7d319c96d2514c3b11f27a7e85b7c408a79d
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|
| |
|
|
|
|
|
|
|
| |
Disable for INTEGRITY AND VXWORKS as it is currently not supported for
these two targets
Pick-to: 6.10
Change-Id: I7eb21d5c348f7e29c2c99cede30a8e627036b220
Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
The text layout in this example has annoyed me for a while.
I liked it better when each link was a list item, which used to be the
case before a96871eac888e0c01b29d092bafa80755f1fb47a.
Pick-to: 6.10
Change-Id: I68a6570dbc6c30e63b9d5b8b8079c9a58ab4e728
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-Fixed the path to the example.
-Reduced the example image resolution to improve the layout.
-Explained that the QML is defined in main.qml and second.qml.
-Include XML layout snippets and info.
-Added the imports for the qml types to the snippets and explained them.
-Added a link to the Qt Academy course.
Fixes: QTBUG-138219
Pick-to: 6.10
Change-Id: I9d59bc1b5b63a3d6a8230cdd83b99efd886744d5
Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This updates weatherforecast and vectorimage examples to
use the automatic svgtoqml build steps instead of manual
conversion.
Removes .pro file for weatherforecast. This is a new
example after the move to CMake and it should have
never had a .pro file to begin with. We aren't going
to implement the svgtoqml build step with qmake, so we
can't keep this working.
Task-number: QTBUG-128915
Change-Id: I2e2506316d4fc8fb35c227309f50e0c92f2a0e38
Reviewed-by: Eirik Aavitsland <eirik.aavitsland@qt.io>
|
| |
|
|
|
|
| |
Pick-to: 6.10
Change-Id: Ie189960af25a33f0dee54fbd49213f9d5eab5891
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
The Text::wrapMode has been referenced incorrectly as Text::wrap and
its corrected in this patch.
Fixes: QTBUG-137733
Pick-to: 6.10
Change-Id: Ieb1ab02e19bc929f103443f0845a8980daceb245
Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
The svgtoqml tool has been updated, so we need to update its
generated files as well.
Pick-to: 6.10
Change-Id: Ie58653c35e99e0c1119a9bf64d803371d31261e5
Reviewed-by: Eirik Aavitsland <eirik.aavitsland@qt.io>
Reviewed-by: Hatem ElKharashy <hatem.elkharashy@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Like other examples already do. It would have prevented (at least
when CMake is used, not qmake) problems like in the associated
bug report where .qsb files from newer versions were cherry picked
to older Qt branches that cannot load them.
Pick-to: 6.10 6.9 6.8
Task-number: QTBUG-135407
Change-Id: I25bf69139de13a70e3682865dd779e0a5ab05e28
Reviewed-by: Andy Nichols <andy.nichols@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
While at it, also remove hardcoded application version in main.cpp:
Qt can retrieve this from the application metdata.
Also use camel-case for the project name, according to
https://contribute.qt-project.org/quips/13
Pick-to: 6.10
Change-Id: If73fd741e330b66ae5367a61c65ccc65653cdab6
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
|
|
|
|
|
| |
Pick-to: 6.10 6.9 6.8
Fixes: QTBUG-136611
Change-Id: If2a0a0365ca24360d850ffce98c0bec4a3961976
Reviewed-by: Jonas Karlsson <jonas.karlsson@qt.io>
|