Jump to content

  • Log In with Google      Sign In   
  • Create Account

Interested in a FREE copy of HTML5 game maker Construct 2?

We'll be giving away three Personal Edition licences in next Tuesday's GDNet Direct email newsletter!

Sign up from the right-hand sidebar on our homepage and read Tuesday's newsletter for details!


We're also offering banner ads on our site from just $5! 1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


[Windows] Shortcut key problems


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
2 replies to this topic

#1 Juliean   GDNet+   -  Reputation: 2692

Like
0Likes
Like

Posted 05 October 2013 - 08:34 AM

Hello,

 

while working on my custom shortkey system for my gui, I encountered a few problems with certain key combinations not being recogniced by the messages I'm processing. I was using the WM_KEYDOWN and WM_KEYUP messages to record the states of the CTRL, SHIFT, and ALT key, and WM_CHAR for executing the command. I want the system to be platform indepedant, so I'm dispatching this information via my input handler. Now, when processing the ALT key I came across the WM_SYSKEYUP, WM_CHAR etc.. messages I needed to process. OK, so far so good.

 

But now there is certain combinations not being recognized at all. For example, most combinations with CTRL+ALT fire neigther the SYSCHAR nor the CHAR message. Is there some additional message I need to process, or some other way to tell windows to let those key combinations through?



Sponsor:

#2 wintertime   Members   -  Reputation: 1798

Like
1Likes
Like

Posted 05 October 2013 - 08:48 AM

The WM_(SYS)CHAR messages are not for keys but for textinput and they get generated by TranslateMessage from the other messages in some contrived way, thats why you get problems. You better just use WM_KEYDOWN and WM_SYSKEYDOWN.



#3 Juliean   GDNet+   -  Reputation: 2692

Like
0Likes
Like

Posted 05 October 2013 - 10:11 AM

The WM_(SYS)CHAR messages are not for keys but for textinput and they get generated by TranslateMessage from the other messages in some contrived way, thats why you get problems. You better just use WM_KEYDOWN and WM_SYSKEYDOWN.

Weird, I'm pretty sure I checked if the keydown message was send and it didn't happend... oh well, it works now, thanks!






Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS