kdeglobals's [Colors:*] sections (added last commit) turned out not to be
what colors a plain Qt6 widget like Dolphin: hyprland.lua sets
QT_QPA_PLATFORMTHEME=qt6ct, which makes Qt load its whole QPalette from
qt6ct's own color scheme file instead of asking KDE Frameworks for one.
kdeglobals still matters for KDE/Plasma-integration bits, just not this.
New theme/templates/qt6ct/ renders that file (a serialized QPalette, one
color per Qt::ColorRole - mapped against qpalette.h, not guessed) to
~/.config/qt6ct/colors/aether-rice.conf, the path qt6ct.conf already pointed
at. A few roles (Light/Midlight/Dark/Mid/Shadow/AlternateBase/NoRole/
ToolTipBase/HighlightedText) have no equivalent in colors.toml and reuse the
same static shades already left unmapped in kdeglobals.
Confirmed by restarting Dolphin: an already-open window keeps its old colors,
a fresh one immediately reflects the live palette. README now says plainly
which of the two files actually drives Dolphin's colors, and that a restart
is needed either way.
Also committing the current rendered outputs (colors.toml has been edited
live via the widget/presets since the last commit).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dujsk9jYfxUVLtb5B8eC94