Shoutbox

quote:

---

Originally posted by SpunkyLoveMuff
I'm not using a child window, I don't know about roflmao though

---

Hmm, look at  WM_SYSKEUP Notification (), it's interesting:

quote:

---

WM_SYSKEYUP Notification

The WM_SYSKEYUP message is posted to the window with the keyboard focus when the user releases a key that was pressed while the ALT key was held down. It also occurs when no window currently has the keyboard focus; in this case, the WM_SYSKEYUP message is sent to the active window. The window that receives the message can distinguish between these two contexts by checking the context code in the lParam parameter.

---

You might give it a try , I don't know if it works; I believe I have successfully intercepted WM_KEYUP with arrow keys when I coded some WndProc in C, like some years ago.

No joy yet...

quote:

---

Originally posted by Debug

Script has been stopped           
Script is starting                   
Script is now loaded and ready       

Message: wParam - lParam
                                   
274: 61458 - 25887288               
273: 8146 - 263166             
273: 8146 - 263166             
274: 61696 - 0                     
278: 9241369 - 0               
287: 546308096 - 9241369       
289: 2 - 0                             
289: 2 - 0                         
287: -65536 - 0                     

---

I registered every message from 200-300 and these are the only messages that showed.

274 is me clicking the window
273 is sent on either pressing SPACE or RETURN
274 - 289 is ALT
289 - 287 is ALT again

quote:

---

Originally posted by Mnjul
Well, I am not sure (and could possibly be wrong!), but does your window you register for message notification has a child window (such as a control like a textbox) focused? I remember in this situation, the window itself won't process/receive WM_KEYUP.

---

nope, you're not wrong...

The WM_KEYUP message (and the likes) is send to the control, not to the window which you subclassed with PlusWnd::RegisterMessageNotification.

If you want to catch this message you would need to subclass the control, not the parent window.....

You can also try Registering these keys as hotkeys and unregistering them when the window loses the focus.