Jump to content
Sign in to follow this  
alexischeng

DllCall to enrich Au3 functions

Recommended Posts

alexischeng

Larry,

Just an idea for the DLLCALL, since yu can wait until all the functions added into the Au3 before yu can be lunch a release version. Why not just update a list for the dllcall so that yu can enrich the functions Au3 later after the offical release.

Just an example:

For the functions in Au3 like FileCopy

it can use the api function:

Private Declare Function CopyFile Lib "kernel32.dll" Alias "CopyFileA" (ByVal lpExistingFileName As String, ByVal lpNewFileName As String, ByVal bFailIfExists As Long) As Long

;Copy a file called test.bat to test1.bat

it can be DLLCALL ("kernel32.dll","int","CopyFile","str","test.bat","str",test1.bat")

So now, yu can delete the function for FileCopy, and add the file copy in Appendix saying that user can use dllcall to have filecopy. The adventage is the menu is getting smaller, and people can enrich the function without alter the offical release.

It's just an idea, pls commend in advance

Alexis Cheng,

Share this post


Link to post
Share on other sites
this-is-me

Which is shorter for the coder?

DLLCALL ("kernel32.dll","int","CopyFile","str","test.bat","str",test1.bat")

or

#include <filefunctions.au3>
_CopyFile("test.bat", "test1.bat")

or

FileCopy("test.bat", "test1.bat")

Obviously the last is easiest (no change).


Who else would I be?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.