summaryrefslogtreecommitdiffstats
path: root/mobile-widgets/qml/ThemeTest.qml
diff options
context:
space:
mode:
authorGravatar Jan Mulder <jlmulder@xs4all.nl>2017-11-19 19:27:45 +0100
committerGravatar Jan Mulder <jlmulder@xs4all.nl>2018-02-17 21:05:33 +0100
commitbd10a8442a25bbaa9d6c8256c486af45440d2886 (patch)
tree2a8b99660f176cc026e23ff910986c9c0c46e047 /mobile-widgets/qml/ThemeTest.qml
parentd5d830eac07311e3a920acabd8b94fd3d21d1db1 (diff)
downloadsubsurface-bd10a8442a25bbaa9d6c8256c486af45440d2886.tar.gz
Mobile QML: main.qml to Kirigmi 2.2
This is a long standing issue. I wish to keep up with Kirigami developments including new versions of their controls, but this is not always easy. While we upgraded to Kirigmi 2.2 for most of our QML earlier, using this new version of main.qml breaks numerous stuff. In fact, so much that we just needed to wait. With the progress in Kirigmi, it is now possible to upgrade, with still some issues on our side to be fixed, but this is manageble now. The main show-stopper was a construct to set our theme colors, for example: Kirigami.Theme.highlightColor = Qt.binding(...) This is not posssible any more, as the Kirigami.Theme has made these readonly on their end. This commit just removes the assignments to the now readonly theme items. And the setting of a correct theme color for the action button. Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
Diffstat (limited to 'mobile-widgets/qml/ThemeTest.qml')
0 files changed, 0 insertions, 0 deletions