Enable nullable reference types

[RyanLua]

Description

This pull request includes several changes to the FluentAutoClicker project to enable nullable reference types and improve code quality by handling potential null values. The most important changes include enabling nullable reference types in the project file, updating various class members to be nullable, and modifying event handlers and method parameters to handle nullable values.

Related Issues

Closes #40

Changes Made

Enabling nullable reference types:

• FluentAutoClicker/FluentAutoClicker.csproj: Enabled nullable reference types by adding <Nullable>enable</Nullable>.

Handling potential null values:

• FluentAutoClicker/App.xaml.cs: Changed the Window property to be initialized with a non-nullable value and removed its redundant declaration. [1] [2]
• FluentAutoClicker/Helpers/AutoClicker.cs: Updated the _autoClickerThread field to be nullable.
• FluentAutoClicker/Helpers/WindowMessageHook.cs: Made several changes to handle nullable values in event handlers and method parameters, including Message event, hook in SubclassProc, ToString, Equals, and GetHandle method. [1] [2] [3]
• FluentAutoClicker/Program.cs: Modified method parameters and local variables to handle nullable values, including lpName in CreateEvent, sender in OnActivated, and keyInstance name. [1] [2] [3]

Checklist

• 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

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Files

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

Files not reviewed (1)

• FluentAutoClicker/FluentAutoClicker.csproj: Language not supported

Comments suppressed due to low confidence (2)

FluentAutoClicker/Program.cs:109

• The process.MainWindowHandle may be IntPtr.Zero if the process does not have a main window. This could cause SetForegroundWindow to fail. Consider adding a check to ensure process.MainWindowHandle is not IntPtr.Zero before calling SetForegroundWindow.

_ = SetForegroundWindow(process.MainWindowHandle);

FluentAutoClicker/Helpers/WindowMessageHook.cs:93

• The 'hook' variable can be null here. Add a null check before invoking 'hook.OnMessage(hook, e);'.

hook.OnMessage(hook, e);