| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The pill inverts on hover, so one mark could never work: filled dark it
vanished on the dark hover background, filled light it would vanish on the
accent pill at rest. Both halves of that shipped, one after the other.
Removing the hover rule did not help either, because the GTK theme paints its
own hover shade on the button node underneath. Declining to set a background
does not leave the pill alone, it leaves that shade in charge.
So the mark moves out of the image module and into CSS, where a
background-image can be swapped per state: dark on the accent pill at rest,
light on the dark pill hovered, with the hover background set explicitly
rather than left to the theme. install.sh generates both tints from one source
file, so they cannot drift apart in shape.
That makes the launcher a custom module, since an image module's path is read
once and CSS cannot reach inside it. Its format is a single space for the
usual reason: an empty one draws no widget at all.
install.sh also removes the file the old image module left behind. The prune
only clears dangling symlinks, and that one was written as a real file, so
nothing had been removing it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
Three faults stacked on the same pill, each hidden by the one before it.
A module's `path` is not shell-expanded the way `exec` is, so "$HOME/..."
was taken literally, no file was found, and the module drew nothing without
logging why. The module file is generated into place now, with the absolute
path written in, which is why install.sh removes the target first: an
earlier install had symlinked that file, and a redirect onto a surviving
link truncates the link's target, which is the repo's own copy.
With a real path to try, gdk-pixbuf then refused the file. The XML was
well-formed, but the loader sniffs the opening bytes for "<svg" to choose a
decoder, and the licence comment sat in front of the root element. The
comment is inside the SVG now, and a note in the file says why it has to
stay there.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
A custom module renders nothing at all when its format is empty, and the
format has to be empty because the Slackware mark is an icon rather than
text, so the launcher pill never appeared. It is an image module now, which
takes a path and needs no label: the same reason the language flag is one.
install.sh only ever added links, so the module file this replaces left a
dangling symlink behind that every later install would step over. It now
prunes links whose source has gone, and a reinstall repairs itself.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
