You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not quite exactly sure what happens here. But I have an Uno-App that has a SKXamlCanvas filling nearly the whole screen. On my desktop, it works as expected. But running the app on a Surface device (with presumably different screen-size/DPI/whatever) the PointerWheelChanged-Event only gets invoked when the mouse pointer is in the top left corner of the Canvas. It feels like it is only nearly respecting half of the screen size.
The content rendered uses the whole screen, though, and other events like PointerDown get invoked correctly above every part of the canvas.
I'm using SkiaSharp.View.WinUI and SkiaSharp.Views.Uno.WinUI both in version 2.88.7.
Description
I'm not quite exactly sure what happens here. But I have an Uno-App that has a SKXamlCanvas filling nearly the whole screen. On my desktop, it works as expected. But running the app on a Surface device (with presumably different screen-size/DPI/whatever) the PointerWheelChanged-Event only gets invoked when the mouse pointer is in the top left corner of the Canvas. It feels like it is only nearly respecting half of the screen size.
The content rendered uses the whole screen, though, and other events like PointerDown get invoked correctly above every part of the canvas.
I'm using SkiaSharp.View.WinUI and SkiaSharp.Views.Uno.WinUI both in version 2.88.7.
Code
Expected Behavior
The PointerWheelChanged-event gets raised in every location.
Actual Behavior
No response
Version of SkiaSharp
Other (Please indicate in the description)
Last Known Good Version of SkiaSharp
Other (Please indicate in the description)
IDE / Editor
Visual Studio (Windows)
Platform / Operating System
Windows
Platform / Operating System Version
No response
Devices
No response
Relevant Screenshots
No response
Relevant Log Output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: