diff options
author | Mitch Curtis <mitch.curtis@qt.io> | 2020-08-27 13:28:07 +0200 |
---|---|---|
committer | Mitch Curtis <mitch.curtis@qt.io> | 2020-09-10 12:31:45 +0200 |
commit | bb333700054e4c1e699d907e67f4e6be498968a1 (patch) | |
tree | 79a3b2da09a0be44390c431c58cdec5fbbfcb28e /tests | |
parent | da812ccccea0c7a246bc00bba2df4a54a57cfc96 (diff) |
Fix examples' usages of styles
After the type registration changes, importing a style explicitly
will cause that style's QML types to be used, so applications
should put style-specific code into file-selected directories if
they need to support multiple styles.
[ChangeLog][Important Behavior Changes] Due to the recent type
registration changes, importing a style explicitly (e.g.
"import QtQuick.Controls.Material") now registers that style's
QML types in addition to making its API (attached, singleton, etc.)
available. For this reason, it is now advised to have style-specific
code in a separate QML file and use file selectors if your application
supports more than one style. If your style only supports one style,
importing that style explicitly will work as expected.
For example, if you use Material.foreground in your QML code and your
application supports more than one style, you should refactor the code
that uses the binding into its own file; e.g.
+Material/MyComponent.qml.
Fixes: QTBUG-86263
Change-Id: I38e40ff4f20f61218550ad73945dafb912193466
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions