Custom Query (3927 matches)

;; DirCreate() exeption:
;; DirCreate($path) strips trailing backslash from $path-variable.
;; autoit(3.2.13.1)
;; Not Effected autoit(3.2.12.1)
;; @OSVersion = WIN_XP
;; @OSBuild = 2600
;; @OSServicePack = Service Pack 3
;; @ProcessorArch = X86

$TextDump = ''
$TextDump &= '@AutoItVersion = ' & @AutoItVersion & @CRLF

$var1 = "NewFolder1"
$var2 = "NewFolder2\"
$var3 = "NewFolder3\b"

$TextDump &= '$var1 = ' & $var1 & @CRLF
$TextDump &= '$var2 = ' & $var2 & @CRLF
$TextDump &= '$var3 = ' & $var3 & @CRLF

If Not DirCreate($var1) Then $TextDump &= 'Err: DirCreate($var1)' & @CRLF
If Not DirCreate($var2) Then $TextDump &= 'Err: DirCreate($var2)' & @CRLF
If Not DirCreate($var3) Then $TextDump &= 'Err: DirCreate($var3)' & @CRLF

$TextDump &= '$var1 = ' & $var1 & @CRLF
$TextDump &= '$var2 = ' & $var2 & @CRLF
$TextDump &= '$var3 = ' & $var3 & @CRLF

ClipPut('[' & $TextDump & ']')
MsgBox(0, "$TextDump", '[' & $TextDump & ']')

;~ --- output ---
;~ [$var1 = NewFolder1
;~ $var2 = NewFolder2\
;~ $var3 = NewFolder3\b
;~ $var1 = NewFolder1
;~ $var2 = NewFolder2
;~ ---

Adding as an issue that I need to do some more extensive testing with RunAs() to confirm all the bugs are gone.

From the help file:

If handle is invalid, an AutoIt runtime error will be thrown, and the script will terminate!

First of all, i think none of built-in functions should not to hard crash the script. But if it's really inevitably, those functions should (optional?) recieve handle ByRef, and change the $handle to 0 after it's releasing the CallBack. Something like this:

Func _DllCallbackFree(ByRef $Handle)
	If $Handle > 0 Then
		DllCallbackFree($Handle)
		$Handle = 0
		Return
	EndIf
	
	Return -1
EndFunc

Because for now there is a chance that our script can crash when it's not supose to (in the middle of some task).

Thanks.