16,004,564 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
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