Problem with WM_COMMAND and Arrays

[MaxEdman]

Hello,

I'm using AutoIT v 3.3.10.2. Hopefully this version is late enough. I just checked for updates and saw the new 3.3.12.0. But I don't think that will solve my issue.

The problem I'm having is that when I'm handling an array used in a WM_COMMAND function AutoIT just stops responding.

Hopefully the code below is enough to understand the problem. Both _ArrayDisplay($arr_earlier_errands_2) and _showMyErrandsGUI($arr_earlier_errands) arrayfunctions makes AutoIT tonot respond. If I use the exact same code outside the function "_WM_COMMAND_FUNC" it will work properly. I'm using my SQL-functions all over the script without any problem. But at this point it just won't work. I'm starting to get frustrated.

Anyone have a sollution?

Thanks!

Max Edman

expandcollapse popup

GUIRegisterMsg($WM_COMMAND, "_WM_COMMAND_FUNC")
Global $input_mobilenumber = GUICtrlCreateInput("", 216, 139, 201, 26, BitOR($GUI_SS_DEFAULT_INPUT,$ES_NUMBER))




Func _WM_COMMAND_FUNC($hwnd_main, $imsg, $iwParam, $ilParam)
    Local $setHK = False
    Local $nNotifyCode = BitShift($iwParam, 16)
    Local $nID = BitAND($iwParam, 0x0000FFFF)
    Local $hwnd_GUICtrl = $ilParam

;~  ; Hanterar enbart de meddelanden
    If $nNotifyCode = $EN_CHANGE Then
        If $hwnd_GUICtrl = GUICtrlGetHandle($input_mobilenumber) Then
            Local $s_mobile_number = GUICtrlRead($input_mobilenumber)
            If StringRegExp($s_mobile_number, "\A(07[0-9]{8})") And StringLen($s_mobile_number) = 10 Then
;~  ; Om värdet för mobilnummer uppfyller kraven för hur ett mobilnummer ser ut så söks detta igenom i databasen.
                Local $obj_SQL_conn = _SQL_connect_Automate_Levstat()
                Local $i_number_of_records = _SQLCountRows($obj_SQL_conn, "*tableName*", "*colName", $s_mobile_number)
;~  ; Hittas inga ärenden på detta mobilnummer så returneras 1 direkt.
                If $i_number_of_records = 0 Then
                    _SQLDisconnect($obj_SQL_conn)
                    Return 1
;~  ; Annars ställs frågan om användaren vill se dessa ärenden.
                ElseIf $i_number_of_records > 0 Then
                    If MsgBox(BitOR(4, 32, 262144), "", "*SomeQuestion*") = 6 Then
                        Local $s_SQL_query = "SELECT * FROM *tableName* WHERE " & '*colName*"=' & "'" & $s_mobile_number & "';"
                        ConsoleWrite($s_SQL_query & @CRLF)
                        Local $arr_earlier_errands_2 = _SQLGetArray($obj_SQL_conn, $s_SQL_query)
                        If @error Then MsgBox(0, "", "Funktion: _SQLGetArray" & @CRLF & @error & @CRLF & @extended)
                        _SQLDisconnect($obj_SQL_conn)
                        _ArrayDisplay($arr_earlier_errands_2)
                        _showMyErrandsGUI($arr_earlier_errands)
                        Return 1
;~                      
                    Else
                        Return 1
                    EndIf ; <== If MsgBox(BitOR(4, 32, 262144), "", "*someQuestion*") = 6 Then
                EndIf
            EndIf ; <== If StringRegExp($s_mobile_number, "\A(07[0-9]{8})") Then

        EndIf ; <== If $hwnd_GUICtrl = GUICtrlGetHandle($input_mobilenumber) Then
    EndIf ; <== If $nNotifyCode = $EN_CHANGE Then
EndFunc  ;==>My_WM_COMMAND

Edited July 29, 2014 by MaxEdman

[jchd]

When you are inside the function, the message pump is locked and subsequent messages are queued. You must return as quickly as possible so that normal Windows processing can continue. There is a warning in GUIRegisterMsg about this. It certainly isn't the place to connect to a remote SQL engine and query it!

Also the lockup occurs when you try to affect the GUI: the message pump is waiting for your function to return (quickly) but instead you instruct it to perform actions (_ArrayDisplay, MsgBox and such) that queue in the locked message pump. You have created a deadlock condition.

[MaxEdman]

When you are inside the function, the message pump is locked and subsequent messages are queued. You must return as quickly as possible so that normal Windows processing can continue. There is a warning in GUIRegisterMsg about this. It certainly isn't the place to connect to a remote SQL engine and query it!

Also the lockup occurs when you try to affect the GUI: the message pump is waiting for your function to return (quickly) but instead you instruct it to perform actions (_ArrayDisplay, MsgBox and such) that queue in the locked message pump. You have created a deadlock condition.

 

Ok! Thanks.

What is the smartest way of get the Returnmessage from this function? So that I can continue my coding when the above is correct?

[j0kky]

There is an useful tutorial about GUIRegisterMsg!

[MaxEdman]

There is an useful tutorial about GUIRegisterMsg!

Sorry, my bad! The tutorial was very helpful!

Thanks!