Open TopperDEL opened 1 year ago
Is this something I could tackle on my own? If yes, may someone guide me where I could start? This is a show-stopper on my end, so I would love to get a fix asap and am willing to help resolve this. Thank you!
On iOS (and mac catalyst) we support only "touch" inputs and we "inject" the PointerEnter
when the finger starts to touch the screen (https://github.com/unoplatform/uno/blob/master/src/Uno.UI/UI/Xaml/UIElement.Pointers.iOS.cs#L129).
Adding support for "hovering" requires:
OnNativePointerEnter(args)
and OnNativePointerExited(args)
;Definitely not a simple one :)
GitHubBuild Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported. - uno/UIElement.Pointers.iOS.cs at master · unoplatform/uno
Apple Developer DocumentationSupport pointer interactions in your custom controls and views.
Thanks! I'll see if I can tackle this after the holidays. But it really sounds though - if anyone can solve this before me would be absolutely ok. :) I'll comment here whenever I start.
I just came back to the current state of Uno in Mac Catalyst. This issue still persists. I discussed this with @jeromelaban in this discussion.
This part is crucial to my app but I'm unable to fix the issue as discussed above.
May I ask for a higher prioritization of this issue? Thank you!
Current behavior
The following PointerEvents do not work on MacCatalyst:
Pointerentered
PointerMoved
PointerExited
Expected behavior
The events work as expected.
How to reproduce it (as minimally and precisely as possible)
Here is a githubrepo: https://github.com/TopperDEL/MacPointerEvents
The same is attached as Zip-File: MacPointerEvents.zip
Workaround
None yet, unfortunately
Works on UWP/WinUI
Yes
Environment
Uno.WinUI / Uno.WinUI.WebAssembly / Uno.WinUI.Skia
NuGet package version(s)
4.8.24
Affected platforms
Mac Catalyst
IDE
Visual Studio for Mac
IDE version
17.5.6 build 3
Relevant plugins
No response
Anything else we need to know?
I highly need this for an app. If there is an easy way to deploy to "MacOS" instead of "MacCatalyst" as a workaround, I would be glad to know how to do it.