Add settings page

[RyanLua]

Description

Adds a new settings button to the right of the start button.

Contains the following settings:

• App theme
• Backdrop material
• Always on top
• Notification badge
• App info

Numerous general improvements have been added as well.

Related Issues

Closes #31
Closes #42

Changes Made

This pull request includes various updates to the FluentAutoClicker project, focusing on refactoring, new feature additions, and improvements to existing functionalities. The most important changes include the introduction of a new IsEnabledTextBlock control, updates to the MainPage.xaml layout, and modifications to the App.xaml and App.xaml.cs files.

Refactoring and Code Improvements:

• FluentAutoClicker/App.xaml: Removed unnecessary xmlns:local namespace declaration.
• FluentAutoClicker/App.xaml.cs: Removed inheritance from Application class and simplified the OnLaunched method. [1] [2]

New Features:

• FluentAutoClicker/Controls/IsEnabledTextBlock/IsEnabledTextBlock.cs: Added a new IsEnabledTextBlock control to manage text block states based on the control's enabled status.
• FluentAutoClicker/Controls/IsEnabledTextBlock/IsEnabledTextBlock.xaml: Defined the style and template for the new IsEnabledTextBlock control.

Layout and UI Enhancements:

• FluentAutoClicker/MainPage.xaml: Updated layout to include new resources and controls, such as IsEnabledTextBlock and AnimatedIcon for settings. [1] [2] [3] [4]

Dependency Updates:

• FluentAutoClicker/FluentAutoClicker.csproj: Updated package references to newer versions and added new dependencies.

Miscellaneous:

• FluentAutoClicker/Helpers/AutoClicker.cs: Improved parameter descriptions and refactored the ClickMouse method to use a switch statement for better readability. [1] [2]

Checklist

• Move strings from hard-coded to resource files
• Add settings saving or move it to an issue
• Fix checkbox binding breaking after pausing clicking
• Update legacy code to use bindings
• I have tested these changes thoroughly.
• I have reviewed my code for any potential errors or issues.
• I have followed the code style guidelines for this project.

Additional Notes

Copilot reviewed 5 out of 17 changed files in this pull request and generated no comments.

Files not reviewed (12)

• FluentAutoClicker/App.xaml: Language not supported
• FluentAutoClicker/Controls/IsEnabledTextBlock/IsEnabledTextBlock.xaml: Language not supported
• FluentAutoClicker/FluentAutoClicker.csproj: Language not supported
• FluentAutoClicker/MainPage.xaml: Language not supported
• FluentAutoClicker/MainWindow.xaml: Language not supported
• FluentAutoClicker/Package.appxmanifest: Language not supported
• FluentAutoClicker/SettingsPage.xaml: Language not supported
• FluentAutoClicker/Strings/en-us/Resources.resw: Language not supported
• FluentAutoClicker/Styles.xaml: Language not supported
• FluentAutoClicker/Themes/Generic.xaml: Language not supported
• FluentAutoClicker/Program.cs: Evaluated as low risk
• FluentAutoClicker/App.xaml.cs: Evaluated as low risk

Comments suppressed due to low confidence (3)

FluentAutoClicker/MainPage.xaml.cs:50

• The 'SetNotificationBadge' method should be tested to ensure it correctly sets the badge notification based on the settings.

SetNotificationBadge(BadgeNotificationGlyph.Paused);

FluentAutoClicker/MainPage.xaml.cs:102

• The 'SetNotificationBadge' method could potentially cause issues if the 'SettingsPage' instance isn't properly initialized. This should be covered by tests.

SettingsPage settingsPage = new();

FluentAutoClicker/Helpers/AutoClicker.cs:8

• Creating a new Random instance inside the loop can lead to less randomness. Move the Random instance outside the loop.

int randomClickOffset = new Random().Next(0, clickOffset);