-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WPF Crash on modern Touchscreen when EnablePointerSupport is enabled #8435
Comments
The logic Min is greater than the Reference: #7069 (comment) |
Seems to be reproducable with the Surface Pro 9 as mentioned in the following comment. |
@dos-ise I do not think the HID descriptor be error in Surface Pro 9. |
@lindexi What is the common denominator then? I have 5 factory new Surface Pro 9 here and this can be reproduced on each of them. Works fine on older Surfaces like Surface 7 |
@dos-ise Just like
The message above means:
And you can use https://github.com/todbot/win-hid-dump tool to dump the HID Descriptor in your devices. |
win hid dump crashed immediately on the surface Seems to be a known issue |
I noticed the same issue on Surface 5, any update? |
@nkolarevic Could you dump HID descriptor? |
05 01 09 02 A1 01 85 02 09 01 A1 00 05 09 19 01 06 0F FF 09 50 A1 01 85 1F 09 60 15 00 25 FF 35 06 FF FF 09 01 A1 01 85 5C 09 05 15 00 25 00 35 06 0B FF 09 0B A1 01 85 2E 09 2E 15 00 25 FF 35 05 01 09 0D A1 01 85 01 09 0D A1 02 05 07 09 E3 06 00 FF 09 01 A1 01 85 10 15 00 25 01 35 00 45 0x05, 0x01, // Usage Page (Generic Desktop Ctrls) // 947 bytes |
@nkolarevic Thank you. And I find some And the code below defined the
|
I saw @lindexi posted this to the MVP mailing list before the holidays. Is this WPF-specific, an issue in underlying .NET, or something deeper? If it's a .NET-wide issue, we can get more attention by getting it over to the broader .NET team. |
Thanks @Psychlist1972, this is connected with WPF. Line 63 in dba1a21
|
@Psychlist1972 Thank you. And as the email says, may I know if the definition or behavior of the Surface device is as expected, or in other words, is the judgment in WPF too strict? |
@lindexi I don't know enough about this standard to be able to say. The comments about WPF getting the wrong data make me think this is lower level than WPF, but @nkolarevic said it's WPF for sure, so I'll defer. |
@Psychlist1972 Thank you. The logic of judgment in WPF may be applicable to outdated touch standard formats and may not necessarily be suitable for modern devices. If modern devices consider this format to be reasonable, it is reasonable for WPF to follow the format updates as well. |
I've asked a friend internally if they know who should look at this. If they find someone appropriate, you'll likely see a reply here. |
Thank you for your help. @Psychlist1972 |
Also have a user with this issue on Surface Pro 9 with EnablePointerSupport on (haven't tried with it off yet). Has anyone figured out yet if this is due to an incorrect value in the HID descriptor or if it is WPF being too strict? They reported the following exception:
|
@aquinn39 Yes, some friends reported the same problem. But I'm not sure if this is Surface Pro problem or WPF |
Description
On a Surface Pro 9 my WPF app crashes when clicking anything.
This seems to be caused by enabling Switch.System.Windows.Input.Stylus.EnablePointerSupport
I have attached an example repo
This was recommend by CefSharp in there Example
See here:
https://github.com/cefsharp/CefSharp/blob/master/CefSharp.Wpf.Example/App.xaml.cs
Reproduction Steps
https://github.com/dos-ise/SurfaceStylusError/tree/master
Expected behavior
Should not crash
Actual behavior
Crashes immediately
Regression?
Can also be reproduced in net4.8
Known Workarounds
No response
Impact
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: