Zac Gaetano
554ab9e570
Some checks failed
CI / build-and-test (push) Failing after 27s
Hover state on Wd.Button.Ghost / Caption / RailIcon / IsoToggle was barely visible — the Wd.SurfaceHover fill (#242424) was only 14 luminance points off the canvas (#0A0A0A) and 16 off the cards (#141414), so the hover state read as 'no change' to the user. Changes: 1. Bumped Wd.SurfaceHover #242424 -> #2A2A2A and Wd.SurfaceActive #2D2D2D -> #363636 across the theme (carries to DataGrid rows etc. with the same too-subtle problem). 2. Added Wd.Button.HoverBg (#33333A) + Wd.Button.PressBg (#3F3F47) — dedicated stronger hover/press fills for buttons specifically. The slight blue tint adds chroma so hover reads obviously distinct from a flat darken. 3. Wd.Button.Ghost hover now also sets BorderBrush=Wd.Accent.Cyan — dual cue (lighter fill + bright cyan border) makes the affordance unmistakable on any surface. 4. Wd.Button.RailIcon hover sets foreground=Wd.Accent.Cyan in addition to the brighter fill (rail buttons have icons, not text — color shift on the icon is the strongest signal). 5. Wd.Button.IsoToggle keeps its status-coded background on hover (LIVE cyan / ERROR coral / NO SIGNAL amber) so at-a-glance state isn't lost; instead bumps to a 2px cyan border for the affordance. Verified: cleanly built, app launches, hover over Refresh button now has obvious brighter fill + tooltip vs. neighbors at rest. |
||
|---|---|---|
| .. | ||
| Assets | ||
| Converters | ||
| Services | ||
| Themes | ||
| ViewModels | ||
| AboutWindow.xaml | ||
| AboutWindow.xaml.cs | ||
| App.xaml | ||
| App.xaml.cs | ||
| GlobalUsings.cs | ||
| HelpWindow.xaml | ||
| HelpWindow.xaml.cs | ||
| MainWindow.xaml | ||
| MainWindow.xaml.cs | ||
| NotesWindow.xaml | ||
| NotesWindow.xaml.cs | ||
| OnboardingWindow.xaml | ||
| OnboardingWindow.xaml.cs | ||
| PresetsDialog.xaml | ||
| PresetsDialog.xaml.cs | ||
| PreviewWindow.xaml | ||
| PreviewWindow.xaml.cs | ||
| TeamsISO.App.csproj | ||