aboutsummaryrefslogtreecommitdiff
path: root/scripts/theme-studio/samples.py
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-18 19:55:33 -0500
committerCraig Jennings <c@cjennings.net>2026-06-18 19:55:33 -0500
commit0890cda100295cbfef7a3f0ad43d0e3c784965cf (patch)
treed604e8eae828b84acb7c1b3f489e20aa1d3d1a01 /scripts/theme-studio/samples.py
parent00aa50de133ac00e0e9657afb884c974240314fe (diff)
downloaddotemacs-0890cda100295cbfef7a3f0ad43d0e3c784965cf.tar.gz
dotemacs-0890cda100295cbfef7a3f0ad43d0e3c784965cf.zip
feat(theme-studio): add mode-line-highlight as an editable face
The mode-line hover box (the raised bevel on clickable mode-line segments) came from mode-line-highlight, a face the studio never managed, so it fell through to Emacs's stock released-button default with no way to change it. I added it to the generated UI face list, between mode-line and mode-line-inactive. The row and box control are already generic over that list, so they appear automatically. build-theme.el's UI emission is generic too, so the elisp side needs nothing. The face isn't in the captured Emacs snapshot, so apply_hover_box_default seeds its box to the raised default in both build_uimap branches. That matches current behavior and leaves the user free to flatten or recolor it. The mock frame previews the hover by wrapping a mode-line segment in the face.
Diffstat (limited to 'scripts/theme-studio/samples.py')
0 files changed, 0 insertions, 0 deletions