I've hit day 16 and 17 of the series where Casey sets up the unified input and moves the PeekMessage call to his own function. I run into the issue where everything works but if I assert that UP/DOWN messages don't enter the main callback, the assert triggers. I'm not sure if this is a difference between back then and now (windows 10) or if it's even really an issue.
Is this really a breaking issue or just something I should keep in mind moving forward? From what I've looked up I don't see a way to deny windows from using the callback for key presses.