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
Regardless of the triggering position, whenever focusing on the "Start Menu" in the system, the msg no longer receives the 0x00FF signal. Whether it's TouchScreen, TouchPad, or Pen, the issue persists. This has been bothering me for a long time. I would like to ask how to solve this problem, so that even when focusing on the "Start Menu" in the system, I can still receive the correct WM_INPUT signals. Thank you.
*My system is win11
The text was updated successfully, but these errors were encountered:
Try to use RawInputDeviceFlags.InputSink instead of RawInputDeviceFlags.ExInputSink.
ExInputSink hints OS that the WM_INPUT will only arrive to your application only when there are no other processes registered for Raw Input.
In case it doesn't work, try to run your app as Admin. Sometimes a process with higher privilege may "eat" (by setting the message to be handled) and stop the WM_PUT message for travelling to other processes.
If both doesn't work, I'm sorry I can't help much.
Regardless of the triggering position, whenever focusing on the "Start Menu" in the system, the msg no longer receives the 0x00FF signal. Whether it's TouchScreen, TouchPad, or Pen, the issue persists. This has been bothering me for a long time. I would like to ask how to solve this problem, so that even when focusing on the "Start Menu" in the system, I can still receive the correct WM_INPUT signals. Thank you.
*My system is win11
The text was updated successfully, but these errors were encountered: