DLL calling in autoit

[Lemonsun 0]

Here is my simple dll function in Delphi

FUNCTION DllMessage( aTitle, aMessage : PChar ) : BOOLEAN;
    var
  c: array[0..800] of Char;
begin
StrPCopy(c, aTitle);
  ShellExecute(Application.Handle, 'open', c, nil, nil, SW_NORMAL);

 end;

I just call it by the following code ..

procedure TForm2.Button1Click(Sender: TObject);
begin
    DllMessage('c:\test.doc',' second parameter ');


end;

And what it does is to pass the first parameter to my dll which is (c:\test.doc) and the dll executes the file .

My question is , can i run this DLL with autoit and pass some parameters as well to autoit .

I could not find related examples ....

i tried this , returns 0.and nothing happens ?? Help appreciated ! thanks !

$result = DllCall ( "SimpleMessageDLL", "", "  DllMessage" , "str", "c:\test.doc" , "str","second parameter " )

[JavaCupiX 0]

You can pass parameters to AutoIt and get them with the $CmdLine array

[Lemonsun 0]

You can pass parameters to AutoIt and get them with the $CmdLine array

You can pass parameters to AutoIt and get them with the $CmdLine array

Can you show me examples ?

[Zedna 200]

$result = DllCall ( "SimpleMessageDLL", "", "  DllMessage" , "str", "c:\test.doc" , "str","second parameter " )

try to use "DllMessage" instead of " DllMessage"

BTW: Why not use Autoit's native ShellExecute() function?

[Lemonsun 0]

$result = DllCall ( "SimpleMessageDLL", "", "  DllMessage" , "str", "c:\test.doc" , "str","second parameter " )

try to use "DllMessage" instead of " DllMessage"

BTW: Why not use Autoit's native ShellExecute() function?

The Auoit functions are great ! . The Purpose is to learn calling delphi DLLs with autoit .

the following two code displays the scripts folder and the first parameter is ignored .

DllCall ( "SimpleMessageDLL", "ptr", "DllMessage" , "string", "" , "string","second parameter " )

DllCall ( "SimpleMessageDLL", "ptr", "DllMessage" , "string", "C:\test.doc" , "string","second parameter " )

[Zedna 200]

Look at _GetLastErrorMessage()

Call it after your DllCall() to see error message.