Skip to content

Conversation

jperrett256
Copy link

One minor arch cracking change, two small win32 fixes. Commit messages should explain details.

I don't believe this project targets ARM platforms right now, and os_mutex_release doesn't seem to be called anywhere, so the arch cracking change and the mutex fix shouldn't have a noticeable impact at the moment.

The "ALT key during WM_CHAR events" commit removes dead code and avoids conditionally acting on an lParam bit that is marked as reserved in the win32 docs (empirically appears to always be 0 - so no observable effects).

NikitaSmith057 and others added 12 commits September 9, 2025 16:59
It appears that keyboard input with the ALT key held does not trigger
WM_CHAR events (only WM_SYSCHAR events).

Moreover, the win32 documentation states that bit 29 (zero-based
indexing) is used to indicate if ALT is held. This would correspond to `bit30`, not `bit29`, as these constant names use one-based indexing.
This makes it clear that the conditions in the deleted code were never
hit, in any circumstance.
The win32 documentation for InitializeCriticalSection makes it clear
that DeleteCriticalSection must be called to clear up resources.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants