aboutsummaryrefslogtreecommitdiffstats
path: root/templates/waybar/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'templates/waybar/README.md')
-rw-r--r--templates/waybar/README.md19
1 files changed, 15 insertions, 4 deletions
diff --git a/templates/waybar/README.md b/templates/waybar/README.md
index 19c220c..a69f228 100644
--- a/templates/waybar/README.md
+++ b/templates/waybar/README.md
@@ -4,10 +4,21 @@ The bar is [waybar-theme-udt](../../../waybar-theme-udt), which lives in its
own repository and its own config directory, `~/.config/waybar-udt/`. This
project supplies only its colours.
-`theme.css` is generated here and copied there by `install.sh`, under a fixed
-name that the bar's stylesheet imports, so switching scheme rewrites the file
-the running bar already reads. There is no import to repoint and no per-scheme
-filename.
+`theme.css` is generated here, but `install.sh` does not copy it there itself:
+it calls the bar's own `install.sh`, with `UDT_PALETTE_DONE=1` so that script
+skips regenerating the palette it has just been handed.
+
+That is because the palette reaches the bar as **three** generated files, not
+one: `styles/theme.css`, `dots.colors` for the two dot scripts, which are bash
+and cannot read `@define-color`, and two tints of the Slackware mark, which
+has to contrast with the accent pill at rest and the dark pill on hover.
+Copying only the stylesheet recoloured every pill and left the dots and the
+mark on the previous scheme's colours. Generating them here instead would mean
+two writers for the same files, drifting apart the moment either is edited.
+
+The call is never fatal: a failure in the bar's install warns and leaves the
+bar on its old colours rather than stopping kitty, Kvantum and Sublime from
+being themed. Same reasoning as `udt-appthemes`.
## What the bar asks for