On Monday, February 29, 2016 9:42:11 PM CET Sven Brauch wrote: > Hey, > > On 02/28/2016 03:58 PM, Luigi Toscano wrote: > > This is what I use: > > export QT_QPA_PLATFORMTHEME=kde > > > > and you need the integration plugin installed. It used to be part of > > Frameworks (frameworksintegration), it will be part of Plasma (but > > hopefully still usable without). > > It isn't, unfortunately. For example, it requires KSNI support, because > for some weird reason that is part of the platform theme. > > So using QT_QPA_PLATFORMTHEME=kde is basically not a viable solution for > any non-plasma desktop out there. Instead you are stuck with a 3rd party > solution like qt5ct to at least set the Qt / icon theme (color scheme is > quite hard already), and there is basically no viable option to get e.g. > KDE file dialogs back (instead of the unusable Qt5 default ones). > > Quite a step back from KDE 4 times right now, unfortunately :/
I'm a little bit surprised by this sub-thread and the reasoning. Apparently nobody is interested in writing and maintaining a qpt-plugin for non-plasma. The Plasma devs are willing to maintain such a plugin and then get complaints that it focuses on Plasma. Seriously? If you think Qt's default is too bad, improve Qt. If you think it needs a more generic qpt-plugin which can be used outside of Plasma: do it. But don't complain to people doing actual work. Cheers Martin
signature.asc
Description: This is a digitally signed message part.
