Rename to PointerEntered and PointerExited

[robloo]

Warning: This is a big breaking change for almost all apps and libraries.

What does the pull request do?

Per discussion in #7907 and issue #8058, this standardizes event naming with WPF/UWP/WinUI as follows:

1. PointerEnter -> PointerEntered
2. PointerLeave -> PointerExited

Several secondary members and unit tests were also renamed to match.

What is the current behavior?

Two pointer events use the non-standardized PointerEnter and PointerLeave terminology.

What is the updated/expected behavior with this PR?

The two pointer events use standardized PointerEntered and PointerExited terminology aligning with other XAML frameworks.

How was the solution implemented (if it's not obvious)?

Find and replace.

Checklist

• Added unit tests (if possible)?
• Added XML documentation to any related classes?
• Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Yes, this is a bad one for breaking changes.

Obsoletions / Deprecations

None

Fixed issues

Closes #8058

[avaloniaui-team]

You can test this PR using the following package version. 0.10.999-cibuild0021393-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

[maxkatz6]

this standardizes event naming with WPF/UWP/WinUI as follows

WPF used MouseEnter. But since we went UWP/WinUI route, I also would prefer PoitnerEntered.

[robloo]

this standardizes event naming with WPF/UWP/WinUI as follows

WPF used MouseEnter. But since we went UWP/WinUI route, I also would prefer PoitnerEntered.

Thanks, that actually would have been a good conversation point in the issue or discussion. It explains where the original naming in Avalonia comes from. I guess it's been too long since I used this in WPF and assumed it was the same as UWP.

Nevertheless, agree that the new "Pointer" term is from UWP/WinUI along with the overall design and event args, multi-touch, etc. So as it is now it is kind-of a mix of WPF + UWP. As you said, it makes sense then just to standardize around the modern terminology and UWP/WinUI design used elsewhere.

[avaloniaui-team]

You can test this PR using the following package version. 0.10.999-cibuild0021402-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]