WM Codes

[Unc3nZureD]

Is there any WM code for getting the following actions?:
 

- GUI Focused

- GUI Unfocused

I tried to have a look at it in the help file, but I couldn't find for both. Maybe I missed something?

[mikell]

WM_SETFOCUS & WM_KILLFOCUS

But checking WinActive is much easier, can't you use it ?

[BrewManNH]

$WM_ACTIVATE will fire off when the window gets activated (focused). You'll get $wParam set to 1 or 2 when the window gets activated or clicked on, and 0 when you lose focus on the window.

[Unc3nZureD]

Thanks I will try, anyways it's easier (and probably some more resource-friendlier) to set up a GUIRegisterMsg then looping a WinActive all the time

[BrewManNH]

This is a piece of code that will show you it in action, it's a stripped down version of the GUIRegisterMsg demo linked in my signature.

expandcollapse popup

#include <GUIConstantsEx.au3>
#include <WindowsConstants.au3>
Global $msg
GUIRegisterMsg($WM_ACTIVATE, "WM_ACTIVATE")
$GUI = GUICreate("Test GUI", 200, 200, -1, -1, BitOR($WS_THICKFRAME, $gui_ss_default_gui, $WS_MAXIMIZEBOX))
$Button = GUICtrlCreateButton("Test", 20, 20)
$Button2 = GUICtrlCreateButton(" Another Test ", 20, 100)
$Slider = GUICtrlCreateSlider(20, 60, 150)
$hSlider = GUICtrlGetHandle($Slider)
$hCheck = GUICtrlCreateCheckbox("test", 20, 150)
$Edit = GUICtrlCreateEdit("", 20, 170, 180)
$hEdit = GUICtrlGetHandle($Edit)
ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $hEdit = ' & $hEdit & @CRLF & '>Error code: ' & @error & @CRLF) ;### Debug Console
GUISetState()
While 1
    $msg = GUIGetMsg()
    Switch $msg
        Case $Button
            MsgBox(0, "", "You pressed the button marked TEST")
        Case $Button2
            MsgBox(0, "", "You pressed the button marked 'Another Test'")
        Case $GUI_EVENT_CLOSE
            ExitLoop
    EndSwitch
WEnd
Func WM_ACTIVATE($hWnd, $iMsg, $wParam, $lParam)
    Local $nNotifyCode = BitShift($wParam, 16)
    Local $nID = BitAND($wParam, 0x0000FFFF)
    Local $hCtrl = $lParam
    #forceref $hWnd, $iMsg, $wParam, $lParam
    Switch $iMsg
        Case $WM_ACTIVATE
            Switch $wParam
                Case 1, 2
                    ConsoleWrite("!Window Activated" & @CRLF)
                Case 0
                    ConsoleWrite("!Window Deactivated" & @CRLF)
                Case Else
                    MsgBox(0, "WM_ACTIVATE ", "GUIHWnd" & @TAB & ":" & $hWnd & @LF & _
                            "MsgID" & @TAB & ":" & $msg & @LF & _
                            "wParam" & @TAB & ":" & $wParam & @LF & _
                            "lParam" & @TAB & ":" & $lParam & @LF & @LF & _
                            "MY_WM_SYSCOMMAND - Infos:" & @LF & _
                            "-----------------------------" & @LF & _
                            "Code" & @TAB & ":" & $nNotifyCode & @LF & _
                            "CtrlID" & @TAB & ":" & $nID & @LF & _
                            "CtrlHWnd" & @TAB & ":" & $hCtrl)
            EndSwitch

    EndSwitch
    Return $GUI_RUNDEFMSG
EndFunc   ;==>WM_ACTIVATE

[Unc3nZureD]

Is there any documentation which describes all theese WM codes including their "return values"

[BrewManNH]

MSDN

Search for the windows message on Google to find the relevant information. The MSDN site is nearly always the first one listed. 

Edited December 31, 2013 by BrewManNH

[Unc3nZureD]

It always show how to use it, not a list what it returns. Probably I'm stupid, but can't find a good one

Found it, however it's much different than I expected

Just if anyone needs it later here's the current link:

http://msdn.microsoft.com/en-us/library/windows/desktop/ms644927%28v=vs.85%29.aspx#windows_messages

Edited December 31, 2013 by Unc3nZureD

[BrewManNH]

It always show how to use it, not a list what it returns. 

 

Really? Because when I searched for WM_ACTIVATE I found this link on MSDN which says exactly what the wParam values will be, which is what I used in the demo above.

[Unc3nZureD]

Oh, I mean a complete list what all the WM messages give generally.

[BrewManNH]

I'm sure there's such a list out there, I just haven't run across one yet. I agree, it would be nice to know which one to use, rather than having to make a generic search for what you're hoping to find.