WM_KEYDOWN with GuiRegisterMsg work only with empty GUI?

[MrCreatoR 73]

Hi all,

I trying to register message WM_KEYDOWN, but it seems that it works only if the GUI is free of Controls... as soon as you create any(?) control, the function not responding anymore:

Global Const $WM_KEYDOWN = 0x0101

$HWnd = GUICreate("KEYDOWN_TEST",400,300)
GUIRegisterMsg($WM_KEYDOWN, "Get_KeyDown")

;$BUTTON = GUICtrlCreateButton("Button",10,10,50,20)

GUISetState()


While 1
    $msg = GUIGetMsg()
    Switch $msg
        Case -3
            Exit
    EndSwitch
WEnd

Func Get_KeyDown($HWnd,$Msg,$wParam,$lParam)
    MsgBox(262144, "", "Code of pressed Key is: " & BitAND($wParam,0xFF))
EndFuncoÝ÷ ÙIÜ¢iÛax­¶Ü­æ­åwܨ»¥Ç¶­~éܶ*'jYb!zyÊ+)­ë,yÒ ¹ë"ajÛaȬmçºÇ­æî¶Ú'«-çèrëÛayc
ÎXج­ê®·~.²)à¡ûaxeÛöî¶+g¢Úh²Èè½éí¯'lk¢
ÚåIëRµ«^×MúB
8SQ/Ûnëb¶ÇËajØ­p¢¹"¶«z+'¢j+yÊ'¶º%±» ¡ñ®'­JÖ­zf²mäázÊ%ºØ¨+-¡ÊÞj×W(ÚèƵêƺ$µ+Zµæ®¶­sdvÆö&Â6öç7Bb33cµtÕô´UDõtâÒ ¢b33c´væBÒuT7&VFRgV÷C´´UDõtåõDU5BgV÷C²ÃCÃ3¤uT&Vv7FW$×6rb33cµtÕô´UDõtâÂgV÷C´vWEô¶WF÷vâgV÷C² ¤uT6WE7FFR ¢b33c´%UEDôâÒuT7G&Ä7&VFT'WGFöâgV÷C´'WGFöâgV÷C²ÃÃÃSÃ# ¥vÆR¢b33c¶×6rÒuTvWD×6r¢7vF6b33c¶×6p¢66RÓ0¢W@¢VæE7vF6¥tVæ@ ¤gVæ2vWEô¶WF÷vâb33c´væBÂb33c´6öÖÖæBÂb33c·u&ÒÂb33c¶Å&Ò¢×6t&÷#c#CBÂgV÷C²gV÷C²ÂgV÷C´6öFRöb&W76VB¶W3¢gV÷C²fײ&DäBb33c·u&ÒÃdb¤VæDgVæ

But why this behaviour? is this a bug of the GuiRegistrMsg, or it is an expecting behaviour of the WM_KEYDOWN message? then why we need it, create controls after GuiSetState is not so practical solution, the user will see "creation process" if there is too many controls.

[MrCreatoR 73]

Ok, i think i found my answer in the help file:

Some controls consume internally specific Windows Message ID, so registrating them will have no effect, e.g; WM_CHAR, WM_KEYDOWN, WM_KEYUP are consumed by an edit control.

To bad

[Richard Robertson 186]

I've seen some cases where control events are allowed to cascade down to the container control. Is that just .Net or does that work outside .Net too?

Edited September 12, 2007 by Richard Robertson