From d8adb44a8f368bc4b9ded7127c67310e35b97290 Mon Sep 17 00:00:00 2001
From: Zac Gaetano <zgaetano@wilddragon.net>
Date: Sun, 10 May 2026 13:36:27 -0400
Subject: [PATCH] Wd.Button.Primary: add disabled / pressed / focus states
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Primary button (Apply Changes, Save Preset, Confirm-Stop-All) had only an IsMouseOver trigger. Disabled state looked identical to enabled — confusing for the most-frequently-disabled button in the app.

- Disabled: drops to Wd.Accent.CyanMuted at 70% opacity + Text.Disabled foreground.

- Pressed: 85% opacity for the brief tap.

- IsKeyboardFocused: matches the hover treatment so tab-cycling lights it.
---
 src/TeamsISO.App/Themes/WildDragonTheme.xaml | 22 ++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/src/TeamsISO.App/Themes/WildDragonTheme.xaml b/src/TeamsISO.App/Themes/WildDragonTheme.xaml
index 0ac3a1e..59fc5cc 100644
--- a/src/TeamsISO.App/Themes/WildDragonTheme.xaml
+++ b/src/TeamsISO.App/Themes/WildDragonTheme.xaml
@@ -214,6 +214,28 @@
                             <Setter TargetName="Bd" Property="Background" Value="{StaticResource Wd.Accent.CyanHover}"/>
                             <Setter TargetName="Bd" Property="BorderBrush" Value="{StaticResource Wd.Accent.CyanHover}"/>
                         </Trigger>
+                        <Trigger Property="IsKeyboardFocused" Value="True">
+                            <Setter TargetName="Bd" Property="Background" Value="{StaticResource Wd.Accent.CyanHover}"/>
+                            <Setter TargetName="Bd" Property="BorderBrush" Value="{StaticResource Wd.Accent.CyanHover}"/>
+                        </Trigger>
+                        <Trigger Property="IsPressed" Value="True">
+                            <Setter TargetName="Bd" Property="Opacity" Value="0.85"/>
+                        </Trigger>
+                        <!--
+                            Disabled state: ghost the cyan to a muted tone +
+                            knock the foreground back. Without this trigger
+                            the disabled Apply button looked just like the
+                            enabled one (Apply Changes is the most-frequently
+                            disabled button in the app — its state has to read
+                            distinctly so the operator knows when changes are
+                            pending vs. when nothing's queued to apply).
+                        -->
+                        <Trigger Property="IsEnabled" Value="False">
+                            <Setter TargetName="Bd" Property="Background" Value="{StaticResource Wd.Accent.CyanMuted}"/>
+                            <Setter TargetName="Bd" Property="BorderBrush" Value="{StaticResource Wd.Accent.CyanMuted}"/>
+                            <Setter TargetName="Bd" Property="Opacity" Value="0.7"/>
+                            <Setter Property="Foreground" Value="{StaticResource Wd.Text.Disabled}"/>
+                        </Trigger>
                     </ControlTemplate.Triggers>
                 </ControlTemplate>
             </Setter.Value>