https://bugs.kde.org/show_bug.cgi?id=480272
--- Comment #8 from Nate Graham <n...@kde.org> --- > Without that env var (i.e., out of the box), it looks even worse, and the > cursor is just as wrong. > So qt5ct is not responsible for the cursor problem. It's not that qt5ct is responsible for the problem; but rather it isn't an automatic fix for the problem. Setting qt5ct makes it your QPT, and thus allows *you* to fix the problem yourself using qt5ct's built-in config UI somewhere. > "QGnomePlatform project is unmaintained a no longer actively developed." :/ > I have qt5-gtk-platformtheme installed. I have no idea if there's anything I > am expected to do beyond > installing it but it doesn't seem to help. You have to set the QT_QPA_PLATFORMTHEME envar to it, rather than qt5ct. I don't know what its technical name is though, sorry. You'll have to figure that our yourself. > I'm not sure if I would call Debian a GNOME-focused distro. It's a "we have > everything" distro, isn't it? > The Qt package can't know which DE I am using. > > Obviously most KDE contributors use KDE as their DE so there's no reason why > they would care about > how their apps look like on GNOME, and I can't blame them for that, it's free > software after all. But it > is unfortunate that this means mixing the best parts of GNOME and KDE is a > lot more work than it > should be. If Qt aims to be "native" in every environment it is started in, I > guess it would be a Qt bug > (or at least feature request) if Qt apps don't look native on GNOME by > default? It would certainly be > a bug if Qt apps looked like this on Windows or macOS... It's not really Qt's fault; rather, there's a bit of a mismatch between how Qt does platform theming, and what people in the non-QT world tend to care about. The way Qt works is that it expects for the environment it's run in to set a QPT that tells it how to integrate Qt apps into that environment so they look and feel correct. This is *how* Qt apps know how to look and feel native in the environment they're run in. But if the environment doesn't bother to provide a QPT, then the integration doesn't happen and Qt apps look and feel junky. Someone needs to write that QPT for their environment, so that Qt apps feel native in it. That someone is by definition not a Plasma user--or else they'd be using Plasma's own QPT. Thus it is a bit of an annoying chore for them; they need to care about consistent theming between apps from different developers and cultures, and have the technical expertise with Qt and time to write a QPT. Clearly GNOME people do not have the interest, skill, and/or time to get it done. That's fine; I can't blame them. So the task basically falls to distro maintainers. In fact this is one of the reasons why distros exist: to *integrate* together all the weird and wacky diverse components that come from different people and groups and projects, so that the final result is reasonably harmonious. Writing a QPT to make Qt apps look and feel nice in a non-Plasma environment is something I would definitely expect of distro developers. Maybe they could even collaborate on it so no one distro has to do it all themselves. In the absence of that, Distros that don't care about this even a little bit could even be lazy and set Plasma-Integration as the QPT for their non-Plasma environments, and then at least Qt apps would be Breeze-themed and look KDE-ish. They wouldn't look native in a GTK environment, but they'd look better than they do when using the default Fusion theme. Hopefully that clarifies the situation. -- You are receiving this mail because: You are watching all bug changes.
