| Git Clone URL: | https://aur.archlinux.org/qt6ct-kde.git (read-only, click to copy) |
|---|---|
| Package Base: | qt6ct-kde |
| Description: | Qt 6 Configuration Utility, patched to work correctly with KDE applications |
| Upstream URL: | https://github.com/trialuser02/qt6ct |
| Licenses: | BSD |
| Conflicts: | qt6ct |
| Provides: | qt6ct |
| Submitter: | ilya-fedin |
| Maintainer: | ilya-fedin |
| Last Packager: | ilya-fedin |
| Votes: | 9 |
| Popularity: | 1.42 |
| First Submitted: | 2023-11-08 18:16 (UTC) |
| Last Updated: | 2024-10-03 05:15 (UTC) |
The patch now also changes kdeglobals to handle the new KF behavior of pushing the default styling more aggressively (https://invent.kde.org/frameworks/kiconthemes/-/issues/3). To get the change, it should be enough to open the configurator and click OK (it will write both the qt6ct config and kdeglobals).
Although, kconfigwidgets has a bug with the widget style key name so it will fully work only starting with KF 6.7.0.
Ok, apparently the PR is not going to be merged any time soon, updated the patch
Here it is: https://github.com/trialuser02/qt6ct/pull/43
I made some cosmetic improvements (KDE color schemes are now marked in the settings UI to differentiate them from qt6ct ones and get the name intended for displaying rather than the file name) there which I will backport here if the PR will get ignored for a long time (which I guess is likely given that they have a little PR sitting around for a month) or if the owner won't like to accept it.
No, the biggest problem at the time was that qt5ct is placed at sourceforge. Now, that there's KF6 and qt6ct-kde exists, I guess I can try to make a pull request to qt6ct at GitHub.
Thank you so much for this. I was going insane trying to figure out why ark was not reading the theme properly. Have you considered trying to get this merged into qt6ct?
This package is gold. Thanks.
@q234rty thanks, I had no chance to test it and only ensured it builds, looks like KColorSchemeManager from KF6 always sets a QString while previously it was setting an empty variant when no custom color scheme is set.
This package does not work for me (on neochat at least). I did a bit of debugging and found that using if(qApp->property("KDE_COLOR_SCHEME_PATH").toString().isEmpty()) instead of if(qApp->property("KDE_COLOR_SCHEME_PATH").isNull()) makes it work.
You're commenting under qt6ct-kde, not qt5ct-kde. The dependency is right
The dependency is now called qqc2-desktop-style5 with the recent renaming of the KF5 packages.
Pinned Comments
ilya-fedin commented on 2023-11-08 18:17 (UTC) (edited on 2024-03-12 00:06 (UTC) by ilya-fedin)
Some user guide:
My patchset contains multiple fixes/features in comparison to vanilla qt6ct:
xdg-desktop-portal allows you to have KDE dialogs in non-KDE environment without installing plasma-integration package. To get them, all you need is:
How to ensure that session dbus instance is running correctly when using xinit (DMs should already do the right thing for you):
for f in /etc/X11/xinit/xinitrc.d/?*.shloop from /etc/X11/xinit/xinitrc to your .xinitrcsystemctl --user status dbusand the service is running. You shouldn't enable the service, it should be activated by dbus.socket.In case of Wayland, you may need to integrate your WM with systemd (that's what one of the scripts in /etc/X11/xinit/xinitrc.d does for X11): https://github.com/swaywm/sway/wiki#gtk-applications-take-20-seconds-to-start