Add advanced animation and trigger options for Next Up and taskbar widget

[FunnyTHEWorld]

This pull request introduces a new advanced animation option for the "Next Up" window, improves the dominant color extraction for images, and enhances user configurability and localization for the taskbar widget and "Next Up" features. The most significant changes include the addition of a customizable animation for the "Next Up" window, a new helper class for image color analysis, and refactoring of the taskbar widget trigger logic and settings.

Key changes:

"Next Up" Window Enhancements

• Added an advanced animation option for the "Next Up" window, including new UI elements and animation-related properties, with a default duration of 2500 ms and a toggle in settings. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]
• Updated the default "Next Up" duration to 2500 ms across all relevant settings and localizations. [1] [2] [3] [4] [5] [6]

Image Processing

• Introduced a new ImageHelper class with methods to extract the dominant color from a BitmapSource, including handling for near-white/black images and accent color extraction.

Taskbar Widget Configuration Improvements

• Refactored the taskbar widget trigger option from a simple toggle to a multi-choice setting (None, OnHover, Click), updated the settings UI to use a ComboBox, and adjusted related property names and logic. [1] [2] [3] [4] [5] [6]
• Updated localization files to reflect the new trigger options and improved descriptions for the taskbar widget interaction. [1] [2]

UI and Settings

• Added a new toggle in the settings window for enabling/disabling the advanced animation for the "Next Up" window. [1] [2]
• Ensured the "Next Up" window is always on top by setting Topmost="True".

These changes collectively improve user experience by providing more customization, a visually enhanced "Next Up" window, and better handling of image colors for UI theming.
Introduces a new advanced animation option for the Next Up window, including a new animation sequence and UI controls. Refactors the taskbar widget trigger from a boolean clickable property to a multi-option trigger type (None, OnHover, Click), updates related UI and localization, and adjusts default durations and settings for improved user experience.

Looks good so far! Thanks for your patience.

Before we merge, there are a few issues:

• 1. While the next up animation looks really good, I think a lot of users might get fatigued waiting 2.5 seconds to see the full details every time the flyout pops out. Perhaps the durationRatios or animation multipliers could be modified to be shorter (see the newly introduced taskbar widget animation in v2.4). We should aim for about 1 second for the full animation. This will get it closer to feel native.

Readjusted animation duration to 1700ms and default window duration was set to 2500ms(Animations will be strange if quicker),and animations are already binded to duration of settings

• 2. We should still add a toggle for the Next Up animations in the settings, although I could handle that if you want to.

Added

• 3. The TaskbarWidgetClickable is not properly migrated to the new settings (false -> 0, true -> 2)

I still not quite get it,TaskbarWidgetClickable was replaced by TaskbarWidgetTriggerType (int, 0 -> flase, 1 -> OnHover, 2 -> true(Click)) and showed in a combobox

QQ20251222-16485-HD.mp4

[FunnyTHEWorld]

Trigger type combobox in Chinese version

[Copilot]

Pull request overview

This PR introduces advanced animation capabilities for the "Next Up" window and refactors the taskbar widget interaction model from a simple boolean toggle to a three-option trigger system (None, OnHover, Click). The changes enhance user customization and visual polish while updating default durations and localization strings across multiple languages.

• Added a sophisticated entrance animation system for the Next Up window with configurable blur effects, transforms, and storyboard sequences
• Refactored taskbar widget trigger from boolean TaskbarWidgetClickable to integer-based TaskbarWidgetTriggerType with three interaction modes
• Introduced ImageHelper class for extracting dominant colors from album artwork to enhance UI theming

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 22 comments.

Show a summary per file

File	Description
FluentFlyoutWPF/Windows/TaskbarWindow.xaml.cs	Refactored click handler to support three trigger types (None, OnHover, Click) and updated brush usage to use theme resources
FluentFlyoutWPF/Windows/NextUpWindow.xaml.cs	Added complex entrance animation logic with configurable duration ratios and integrated ImageHelper for dominant color extraction
FluentFlyoutWPF/Windows/NextUpWindow.xaml	Restructured XAML to support advanced animations with blur effects, transforms, and gradient backgrounds
FluentFlyoutWPF/ViewModels/UserSettings.cs	Added IsNextUpAdvancedAnimationEnabled property, changed TaskbarWidgetClickable to TaskbarWidgetTriggerType, and updated default NextUpDuration to 2500ms
FluentFlyoutWPF/SettingsWindow.xaml	Replaced ToggleSwitch with ComboBox for taskbar widget trigger selection and added new CardControl for animation toggle
FluentFlyoutWPF/Resources/Localization/Dictionary-zh-TW.xaml	Updated default NextUpDuration description from 2000ms to 2500ms
FluentFlyoutWPF/Resources/Localization/Dictionary-zh-CN.xaml	Added localization for advanced animation settings and updated trigger option descriptions
FluentFlyoutWPF/Resources/Localization/Dictionary-en-US.xaml	Added localization strings for trigger types and advanced animation feature with updated descriptions
FluentFlyoutWPF/Classes/ImageHelper.cs	New helper class for extracting dominant colors from images with fallback logic for near-white/black images

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Inconsistent time calculation. The beginSec parameter is multiplied by durationRatio in lines 138, 145, and others, but the multiplication happens inconsistently. For example, line 138 uses startTimePoint1*durationRatio while line 145 uses startTimePoint2 directly (where startTimePoint2 was already computed as 0.5*durationRatio). This creates confusion about whether the time points should be pre-multiplied or multiplied at usage time. Consider either pre-multiplying all time points or multiplying all at usage time for consistency.

[unchihugo]

I still not quite get it,TaskbarWidgetClickable was replaced by TaskbarWidgetTriggerType (int, 0 -> flase, 1 -> OnHover, 2 -> true(Click)) and showed in a combobox

Basically, when existing users update to this version, their interaction preference will be reset since the TaskbarWidgetClickable has been removed. By migrating the setting to the new variable when starting the app (assigning TaskbarWidgetClickable = false to TaskbarWidgetTriggerType = 0, and TaskbarWidgetClickable = true to TaskbarWidgetTriggerType = 2) we can prevent the migration issue. On top of that, let's make TaskbarWidgetTriggerType default to 2.

Copilot worded it nicely as well:

Missing settings migration logic: The property TaskbarWidgetClickable (bool) has been replaced with TaskbarWidgetTriggerType (int), but there's no migration code to convert old user settings. When users upgrade, their existing TaskbarWidgetClickable=true setting will be lost and default to TaskbarWidgetTriggerType=1 (OnHover) instead of migrating to TaskbarWidgetTriggerType=2 (Click). Consider adding migration logic in the RestoreSettings or CompleteInitialization methods to check if an old setting exists and migrate it appropriately: false -> 0 (None), true -> 2 (Click).

[FunnyTHEWorld]

Basically, when existing users update to this version, their interaction preference will be reset since the TaskbarWidgetClickable has been removed. By migrating the setting to the new variable when starting the app (assigning TaskbarWidgetClickable = false to TaskbarWidgetTriggerType = 0, and TaskbarWidgetClickable = true to TaskbarWidgetTriggerType = 2) we can prevent the migration issue. On top of that, let's make TaskbarWidgetTriggerType default to 2.

Got it! my bad, I 've updated and resolved conflicts

[ysfemreAlbyrk]

I hope you merge this PR @unchihugo . 😭 this looks fantastic.