DllCall returns nothing for Interger functions

[Vano]

I'm using autoit to call functions from my custom DLL.

But when calling functions that return Integers, i always get zeros.

I can actually see (in debugger) that the DLL returns integer 1 (and it gets stored in autoit's memory)

but the script keeps displaying 0's or empty strings.

I tries the same with a system DLL and got the same result!

Here's an example script:

MSGBox(0,"", DllCall("kernel32.dll", "int", "GetCurrentProcess"))
MsgBox(0,"",@error)

The same thing if i use 'long' or 'dword' or 'hwnd' instead of 'int'

Looks like is the same problem as Formatting API return result creates problems, Fixed 3.2.3.7

version 3.2.4.9

Edited July 11, 2007 by Vano

[Jos]

Please post questions like this in the Supportforum first to ensure its not a pilot error

DllCall returns an Array thus indeed will show nothing when used in a MsgBox()

Also the Second MsgBox() shos the @error generated by the first MsgBox() NOT the DllCall !

If the function call fails then @error is set to 1. Otherwise an array is returned that contains the function return value and a copy of all the parameters (including parameters that the function may have modified).

$return[0] = function return value

$return[1] = param1

$return[2] = param2

...

$return[n] = paramn

Edited July 11, 2007 by JdeB

[Vano]

If the function call fails then @error is set to 1. Otherwise an array is returned that contains the function return value and a copy of all the parameters (including parameters that the function may have modified).

$return[0] = function return value

...

Dammit. I've read the article for many times but somehow missed this very paragraph

[ChrisL]

Dammit. I've read the article for many times but somehow missed this very paragraph

$ret = DllCall("kernel32.dll", "int", "GetCurrentProcess")
Msgbox(0,"",$ret[0])

Returns -1

$ret = DllCall("kernel32.dll", "hwnd", "GetCurrentProcess")
Msgbox(0,"",$ret[0])

Returns a handle

[Vano]

DllCall returns an Array thus indeed will show nothing when used in a MsgBox()

Also the Second MsgBox() shos the @error generated by the first MsgBox() NOT the DllCall !

That's quite strange, however. If a variable contains a non-empty value, it should also evaluate to something non-empty when converted to string.

[Jos]

That's quite strange, however. If a variable contains a non-empty value, it should also evaluate to something non-empty when converted to string.

No it is not ... any array variable will return EMPTY when referred to without the [x] behind it ....

Moving this thread to Support ....