Using package DeviceId.Wmi - MotherboardSerialNumber gives WPF scroll issues

[PepijnHogervorst]

For a full stack WPF application with multiple projects the DeviceId.Wmi library for some reason gives touch scroll issues when used.

Adding the library as Nuget package to my Infrastructure layer project would make my WPF UI layer project give touch scroll issues. The touch still works but the scrollviewer in particular could not easily be scrolled anymore (PanningMode is set to Both).

I have created a simple project where the issue is active: TestTouchScroll-issue.zip. If you comment the lines in the MainWindow.xaml.cs - line 15 to 18 the problem is fixed. So it has to do something with the .AddMotherboardSerialNumber() or .AddMachineGuid() method that is called. I also found out that removing the MotherboardSerialNumber method fixes the issue. (the MachineGuid method doesn't use the Wmi library, i suspect the problem to lie in the Wmi library).

Hopefully this information is useful enough and feel free to ask for more information if required! Thank you in advance! Great library never the less!

Cheers, Pepijn

[MatthewKing]

That's a very strange one!

Doing a bit of research, I see the following similar issues:

• Using ManagementObjectSearcher in WPF with Core 3.0/3.1 stops Stylus & Touch inputs dotnet/runtime#522
• Issue with touch being disabled when having two windows in two different threads (like a splash screen) dotnet/wpf#2393

I notice a workaround is posted in those issues. Does using that workaround help for your case?

Cheers

[PepijnHogervorst]

Thank you for the quick response. The workaround (adding _ = Tablet.TabletDevices; to the ) does work for the TestTouchScroll project but unfortunately not for the full stack application I am working on. The startup there is more complex (using async). For now I will not use the MotherboardSerialNumber anymore to work around this issue!