Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

60%
+1 −0
Q&A Issues with receiving WM_INPUTLANGCHANGE etc. messages when language is chosen using hotkeys

It seems like changing the window handle to null in PeekMessageW solved the issue: BOOL bret = PeekMessageW(&msg, null, 0, 0, PM_REMOVE); Then I can still get the window handle source like ...

posted 9mo ago by ZILtoid1991‭

Answer
#1: Initial revision by user avatar ZILtoid1991‭ · 2023-08-13T12:20:47Z (9 months ago)
It seems like changing the window handle to null in PeekMessageW solved the issue:

```d
BOOL bret = PeekMessageW(&msg, null, 0, 0, PM_REMOVE);
```

Then I can still get the window handle source like this:

```d
output.handle = msg.hwnd;
```

Win32 API is just really not intuitive, and many behaviors are not well documented.