Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualSik_the_hedgehog

Posted 13 June 2013 - 02:59 PM

Also a quick warning before I forget, you shouldn't just handle WM_KEYDOWN and WM_KEYUP, but also WM_SYSKEYDOWN and WM_SYSKEYUP (you can treat those latter two the same way as the former two, really). The main difference is that the latter trigger when you press F10 or Alt with another key (i.e. the shortcuts that would trigger the menubar). Make sure you're handling all four events, not just the first two.

 

EDIT: also that's what I get for not paying attention, thought the two posts were from the same user =P (which happens quite often too...)


#2Sik_the_hedgehog

Posted 13 June 2013 - 02:58 PM

Also a quick warning before I forget, you shouldn't just handle WM_KEYDOWN and WM_KEYUP, but also WM_SYSKEYDOWN and WM_SYSKEYUP (you can treat those latter two the same way as the former two, really). The main difference is that the latter trigger when you press F10 or Alt with another key (i.e. the shortcuts that would trigger the menubar). Make sure you're handling all four events, not just the first two.


#1Sik_the_hedgehog

Posted 13 June 2013 - 02:57 PM

Then I guess you need to handle the keyboard events.

 

Just a quick warning, you shouldn't just handle WM_KEYDOWN and WM_KEYUP, but also WM_SYSKEYDOWN and WM_SYSKEYUP (you can treat those latter two the same way as the former two, really). The main difference is that the latter trigger when you press F10 or Alt with another key (i.e. the shortcuts that would trigger the menubar). Make sure you're handling all four events, not just the first two.


PARTNERS