4 ms·
I wonder if the incorrectly documented flag behaves the same way in all of the versions of Windows that the game is meant to run on.
by aboodman 12y ago
I wonder if the incorrectly documented flag behaves the same way in all of the versions of Windows that the game is meant to run on.
- to3m 12y agoDirectInput has long supported the DISCL_NOWINKEY flag, which blocks the Windows key and other shortcuts. At one point DirectInput was its own thing, so who knows what that flag did internally; but since Windows XP, DirectInput has been a wrapper round the raw input system, so that flag presumably maps to RIDEV_NOHOTKEYS. Since DISCL_NOWINKEY has always proven reliable for me on Windows XP and later, I'd imagine (unless proven otherwise...) RIDEV_NOHOTKEYS will be reliable too. EDIT: Just to prove me utterly wrong, see here: https://twitter.com/cmuratori/status/470647266995224576 https://twitter.com/cmuratori/status/470647266995224576. Obviously it was some kind of a problem that this flag did pretty much the right thing.