Set QtQuick style independent of compositor
Closed this issue · 4 comments
While looking through the configuration files I noticed that QT_QUICK_CONTROLS_STYLE is only set on kwin_wayland. However it seems that applying a common style for QML based applications should actually work across compositors by installing a style package (qqc2-desktop-style on Arch).
Thus setting QT_QUICK_CONTROLS_STYLE=org.kde.desktop should work independent of the compositor in use right?
The affected script code is here:
lxqt-wayland-session/startlxqtwayland.in
Line 125 in 33b8ec9
It works everywhere and users can add it in Session Settings → advanced.
I don't know if other KDE apps beside systemsettings are affected and this is used only in Kwin sessions.
There is already a paragraph in the Wiki, and I don't think we should integrate QML style in our plugin.
This affects every application using QtQuick controls (those are especially made for Desktop!). Usually I use standalone applicatoins such as Discover to test this.
And no - this doesn't only apply to KWin. I tried this in other DE's (just an hour ago in Cosmic with and without LXQt) and the issue applies there as well.
Adding this by default to ~/.config/lxqt/session.conf makes it probably more obvious to users. Not much of a difference though…
Yes, QT_QUICK_CONTROLS_STYLE can be used with any QML app. However, this is about Wayland, not QML. Users can add it to LXQt Session Settings, in X11 and Wayland alike.
Then why is such variable defined here at all!? This easily creates a false impression on LXQt users that lxqt + kwin works "better" than other combinations.
It is only consequent to remove the variable completely from the startup script in the first place.