Custom Query

Infinite Loop On Exit

I opened this test script and then closed it. When I pressed the close button, it started refreshing the contents all the other open windows. It slowed down my computer so I couldn't do much. Task Manager couldn't close it as it the script was refreshing the window. I could only end it by pressing CTRL + Pause/Break to force quit in Scite.

#include <ButtonConstants.au3>
#include <EditConstants.au3>
#include <GUIConstantsEx.au3>
#include <GUIListBox.au3>
#include <WindowsConstants.au3>

#Region ### START Koda GUI section ### Form=
$Form1 = GUICreate("Form1", 633, 447, 192, 124)
$Edit1 = GUICtrlCreateEdit("", 80, 64, 329, 193)
GUICtrlSetData(-1, "Edit1")
$Button1 = GUICtrlCreateButton("Button1", 88, 280, 105, 25, 0)
$Button2 = GUICtrlCreateButton("Button2", 224, 288, 153, 25, 0)
$List1 = GUICtrlCreateList("", 448, 64, 129, 201)
GUISetState(@SW_SHOW)
$Form2 = GUICreate("Form1", 200, 200, 200, 200, BitOR($WS_SYSMENU,$WS_CAPTION,$WS_CHILD,$WS_BORDER,$WS_CLIPSIBLINGS), BitOR($WS_EX_MDICHILD,$WS_EX_WINDOWEDGE,$WS_EX_LAYERED), $Form1)
GUISetState(@SW_SHOW)
#EndRegion ### END Koda GUI section ###

While 1
	$nMsg = GUIGetMsg()
	Switch $nMsg
		Case $GUI_EVENT_CLOSE
			Exit
	EndSwitch
WEnd

_SQLite_Exec set allway @error to 0 see the Line 3 from the end "If $avRval[5] <> 0 Then DllCall($g_hDll_SQLite, "none:cdecl", "sqlite3_free", "ptr", $avRval[5])" this line overwrite the @error set at the line 5 from the end

Func _SQLite_Exec($hDB, $sSQL, $sCallBack = "")

If $g_hDll_SQLite = 0 Then Return SetError(1, 0, $SQLITE_MISUSE) If Not SQLite_hChk($hDB, $SQLITE_DBHANDLE) = $SQLITE_OK Then Return SetError(2, 0, $SQLITE_MISUSE) Local $avRval, $aResult, $iRows, $iColumns, $iRval If $sCallBack <> "" Then

$aResult = "SQLITE_CALLBACK:" & $sCallBack $iRval = _SQLite_GetTable2d($hDB, $sSQL, $aResult, $iRows, $iColumns) If @error Then Return SetError(3, 0, $iRval) Return $iRval

EndIf $avRval = DllCall($g_hDll_SQLite, "int:cdecl", "sqlite3_exec", _

"ptr", $hDB, _ ; An open database "str", $sSQL, _ ; SQL to be executed "ptr", 0, _ ; Callback function "ptr", 0, _ ; 1st argument to callback function "long*", 0); Error msg written here

If @error > 0 Then

Return SetError(1, 0, $SQLITE_MISUSE) ; DllCall Error

EndIf If $avRval[0] <> $SQLITE_OK Then

SQLite_ReportError($hDB, "_SQLite_Exec", $sSQL) SetError(-1)

EndIf If $avRval[5] <> 0 Then DllCall($g_hDll_SQLite, "none:cdecl", "sqlite3_free", "ptr", $avRval[5]) Return $avRval[0]

EndFunc ;==>_SQLite_Exec after _SQLite_Exec, @error==0

Not really a "bug" but I don't think that declaring $ERROR as const in WindowsConstants.au3 is a very good idea, since you then cannot use variables named $error, which is a very common name to name variables. Just my 2 cents, it sure did cause me some headaches.