gramps
987fddac24
The creator (2026-10-21), on Live -> Layers -> webcam -> Properties:
"why does the drop down under the web cam properties not show the same style for
the border color drop down list box?"
"one of the first things we did was define branding. We established look-and-feel
standards. And yet you keep ignoring these and I'm wondering why"
WHY IT WAS MISSED - the answer the creator is owed.
The TASK 58 sweep had already walked the whole app for un-themed controls and the
border picker STILL was not themed, because the sweep looked for control TYPES
(ComboBox / CheckBox / TextBox) carrying no theme style - and the border picker was
NONE of those. It was a "..." Button whose Click handler built a ContextMenu of
swatches in code. It was never in the sweep's scope, and PropertiesStyleTests.cs
(a type-based guard) could not see it either. A picker that LOOKS like a drop-down
is invisible to a type-based audit; the guard has to ask "is this the app's widget?".
WHAT CHANGED
- The picker is now the app's YtComboBox - the widget the Display and Font pickers
wear - bound to the palette (SelectedElement.BorderColorOptions) with its selection
bound by VALUE (SelectedItem -> BorderColorEntry), because WPF's SelectedValue
matching is ordinal and the palette mixes #FFFFFF and #e94560.
- The closed box shows the swatch + the colour's NAME; the rows show swatch + hex +
name (the rows the creator approved in TASK 60). A ComboBox cannot do that with one
ItemTemplate - WPF copies it into the read-only SelectionBoxItemTemplate - so
Helpers/ClosedBoxTemplateSelector.cs picks by the ContentPresenter's templated
parent: the ComboBox for the closed box, the ComboBoxItem for a row. Verified
against WPF with a throwaway probe, not assumed.
- The swatch is painted by the THEME (Helpers/HexToBrushConverter.cs, registered as
HexToBrush) - the hand-painted SolidColorBrush(Color.FromRgb(...)) in the old
click handler was the exact anti-pattern the theme forbids. The swatch also carries
a 1px #2a3a5e border now, so black and dark swatches are visible on the dark menu
(the follow-up TASK 60 left open).
- The hex field stays (60px, editable): a colour outside the palette can still be
typed, and the drop-down then carries that hex as a NAMELESS entry ("no name" is the
honest answer). The palette's name moved out of TASK 62's TextBlock into the
drop-down's closed box.
- The hand-built menu, its ContextMenu/MenuItem/SolidColorBrush code and
WebcamBorderColorPicker_Click are gone.
MODEL: SceneElement.BorderColorName -> BorderColorEntry (the palette entry for the
current hex, with its name; setting it writes the hex back) + BorderColorOptions (the
palette plus the custom entry), both raised when BorderColor changes.
BorderColorPalette gains EntryFor(hex) and OptionsFor(hex); NameOf delegates.
Guards: ytLive.Tests/BorderColorPickerTests.cs (the ONE test for this change - the
model, the panel, and the REAL widget: with the app's theme style and the panel's own
templates the closed box names the colour and the rows show the hex AND the name).
The TASK 60 guard (BorderColorPaletteTests) was updated because the mechanism it
asserted - a code-built menu - no longer exists; it now guards the new wiring (the
drop-down is bound to the palette and neither the panel nor the code-behind carries a
second list of colours).
Full suite: 435/435 passed, 0 warnings.
2.8 KiB
2.8 KiB
Themes — index
The single source of the dark UI theme. See schema.md for the
memory-map conventions.
| File | Purpose |
|---|---|
Controls.xaml |
All custom control styles/templates: YtButton, YtButtonSecondary, IconButton, YtTextBox, YtTextBoxCompact (the dense variant the properties panel uses), YtComboBox, YtCheckBox, scrollbar/slider/tooltip/context-menu/menu-item/separator/list-item (implicit where app-wide), YtListBoxItem, YtLabel, SectionHeader |
How it's wired:
- Merged once in
App.xaml— app-wide. New windows get the theme automatically; do not re-merge per-window. - Palette: window
#1a1a2e, fields#0f3460, borders#2a3a5e, popups#16213e, accent#e94560, hover#26ffffff, text#e0e0e0.
Gotchas learned the hard way:
MenuItemRolehas noSeparatorvalue — separators are standaloneSeparatorcontrols with their own implicit style.- A custom
ComboBoxtemplate must put theContentPresenter(SelectionBoxItem) inside the ComboBox template, not the ToggleButton template — the latter resolves against the wrong TemplatedParent and renders nothing. - A control with no style renders with the LIGHT WPF system template — a
hand-painted
Background/Foregroundcolours the box but leaves the system border, the system arrow and the white popup list. That is why the Stream Alerts "Display" drop-down looked like it belonged to another app (TASK 58, 2026-10-21). Rule: every control carries a theme style —YtComboBox,YtCheckBox,YtTextBox/YtTextBoxCompact— and paints no colour of its own.ytLive.Tests/PropertiesStyleTests.csfails if that drifts back. ⚠️ But that guard sees only those control TYPES — a picker built as aButton+ a code-builtContextMenuis invisible to it (the border-colour picker was exactly that, TASK 63). A picker that LOOKS like a drop-down must BE the app's drop-down. - The
YtComboBoxpopup sizes to its CONTENT, not to the ComboBox (measured 2026-10-21: the border-colour popup came out 142.7px wide against a 100px ComboBox) — a long row is never clipped, and the popup may be wider than the closed box. Measure, don't guess. - The closed box and the rows of a ComboBox can only differ through an
ItemTemplateSelector— WPF copiesItemTemplateinto the read-onlySelectionBoxItemTemplate, so one template renders in both places. The selector is told them apart by theContentPresenter's templated parent (ComboBox= closed box,ComboBoxItem= a row) — seeHelpers/ClosedBoxTemplateSelector.cs.
Related: Helpers/index.md (custom controls the theme
styles), the XAML files at repo root that consume these styles.