Comments by .:floyd:. (Top 2 by date)

.:floyd:. 2-May-16 11:02am View

Raw Input inspects packages that are enqueued into the hardware input buffer, long before the system converts them into regular Windows messages. If you want to respond to raw input messages (WM_INPUT) and filter out fake input generated from a call to SendInput you cannot do this in your regular keyboard/mouse message handling. This has to take place when handling WM_INPUT messages.

.:floyd:. 27-Feb-16 9:42am View

Reason for my vote of 1 \n You've got this all wrong. As was pointed out in other comments, you aren't allocating a sufficiently large destination buffer. A single Unicode code unit could map to a double-byte ANSI string. And most certainly will, when converting to UTF-8. std::string uses host encoding. On Windows that's an MBCS (ANSI Codepage). And then, the code fails for embedded NUL characters as well. Pretty useless tip, and given that there are conversion macros readily available, it's also needless.

.f