Timeline for Does VK_SNAPSHOT not send a WM_KEYDOWN; only WM_KEYUP?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 2, 2011 at 18:16 | comment | added | user1430 | I missed my edit window, but to clarify, DI talks to RawInput, but does so in a fashion that renders it no more efficient for practical purposes than just using the message loop you already have to have in place anyhow; I should have said this instead of the "higher level" comment. | |
| Dec 2, 2011 at 18:07 | comment | added | user1430 | XInput only provides access to Xbox-style controllers. DirectInput, furthermore, was built on top of other APIs so is actually higher-level than just listening for WM_* messages. One could use the RawInput API in theory, but this is rarely worth it. Win32 messages are the ideal means of dealing with non-Xbox, non-joystick input devices. | |
| Dec 1, 2011 at 13:47 | comment | added | Jonathan Dickinson | XInput then :). | |
| Dec 1, 2011 at 12:53 | comment | added | Cliff Harris | direct input is deprecated, everyone tells me not to use it any more! | |
| Dec 1, 2011 at 11:11 | history | answered | Jonathan Dickinson | CC BY-SA 3.0 |