WinAPIEx UDF

[JohnOne]

Yeah, I love this huge library.

Superb resource.

[bo8ster]

Great lib Yashied. I didn't read all 13 pages so this may be answers but are there any plans to have this in the normal Autoit release or be merged with the WinAPI.au3?

[guinness]

There appears to be a Return error with _WinAPI_PathIsDirectory(), in the documentation it shows 1 if a directory but in fact it Returns 16 on Windows 7 x64. It also appears that MSDN's documentation is a little incorrect too, according to the comments especially >> http://msdn.microsoft.com/en-us/library/bb773621(v=vs.85).aspx

[Mat]

It says on msdn that it returns bool, which is right in that it returns zero or non-zero (16 in this case).

You shouldn't be testing the return value for an exact value anyway, so it shouldn't matter.

[wraithdu]

Well BOOL in C is TRUE or FALSE, which is defined as 1 and 0. Testing for == TRUE or == FALSE is perfectly acceptable when the return is a BOOL. Other API functions return DWORD, INT, UINT, etc and say that success is non-zero. In that case you shouldn't test == TRUE obviously. But here, this is a doc error on MS's part for sure.

[adik2dmax666]

#Include <WinAPIEx.au3>

Opt('MustDeclareVars', 1)


Global $ID = ProcessExists('start.exe')
If $ID > 0 Then 
    ConsoleWrite( _WinAPI_GetProcessFileName($ID) & @CRLF) 
EndIf

What if i have 2 running start.exe on different directories?

Ex. C:\log1\start.exe

C:\log2\start.exe

both have different PID but processexist() only returns the first pid..

[wraithdu]

That's your problem to get the correct PID before using the functions in this UDF.

[AdmiralAlkex]

@adik2dmax666

Then don't use ProcessExist(), use what returns a list.

[guinness]

WinAPIEx is failing when using #AutoIt3Wrapper_Au3Check_Parameters=-d -w 1 -w 2 -w 3 -w 4 -w 5 -w 6

I also think there might be an error in _WinAPI_SetDIBitsToDevice() as $iXDest isn't used at all! I hope you don't mind but I edited my Version for easy debugging of my Programs. For Example in __EnumResLanguagesProc() I used #forceref $hModule, $iType, $iName, $lParam

Edited May 4, 2011 by guinness

[Yashied]

Fixed in next release. Thanks.

Edited May 4, 2011 by Yashied

[guinness]

Thanks Yashied, sorry for being a pain!

[Yashied]

The library has been updated, version remains unchanged.

Changes

• Added the following functions.

  _WinAPI_DWordToFloat

  _WinAPI_EqualMemory

  _WinAPI_FillMemory

  _WinAPI_FloatToDWord

  _WinAPI_GetApplicationRestartSettings

  _WinAPI_GetDeviceGammaRamp

  _WinAPI_LZNTCompress (Thanks trancexx)

  _WinAPI_LZNTDecompress (Thanks trancexx)

  _WinAPI_MoveMemory

  _WinAPI_RegisterApplicationRestart

  _WinAPI_SetDeviceGammaRamp

  _WinAPI_UnregisterApplicationRestart

• Added examples for the functions above.
• Removed the following functions.

  _WinAPI_EqualStruct

  _WinAPI_FillStruct

• Rewrited the following functions.

  _WinAPI_CopyStruct

  _WinAPI_ShellGetSettings

  _WinAPI_ShellSetSettings

  _WinAPI_StructToArray

  _WinAPI_UnionStruct

• Fixed a bug in the _WinAPI_SetDIBitsToDevice() function. (Thanks guinness)
• Updated documentation.

Edited May 22, 2011 by Yashied

[Merrik]

Hi,

I am trying to use this UDF and am having a little bit of a problem.

I am using the _WinAPI_EmptyWorkingSet. It shows in _WinAPI_EmptyWorkingSet([$PID]), yet when I compile it shows syntax error _WinAPI_EmptyWorkingSet([

It complains about the square bracket ([).

If I put _WinAPI_EmptyWorkingSet() - then it compiles fine.

Any help is appreciated.

Thanks,

[AdmiralAlkex]

@Merrik

Square brackets mean that parameter is optional.

[guinness]

Thats because [] means its optional, (same as with the AutoIt Native Functions) so if you want to "Reduce" the Memory of another process then you substitute [] with the PID number e.g. _WinAPI_EmptyWorkingSet(123) otherwise use _WinAPI_EmptyWorkingSet() for the Compiled Script you're using.

Edited June 1, 2011 by guinness

[Merrik]

Thats because [] means its optional, (same as with the AutoIt Native Functions) so if you want to "Reduce" the Memory of another process then you substitute [] with the PID number otherwise e.g. _WinAPI_EmptyWorkingSet(123) or use _WinAPI_EmptyWorkingSet() for the Compiled Script you're using.

Thanks. I thought this was the case, but wanted to make sure since I'm new at this.

[jterwelp]

Is there a way to use this library to get data from the IDENTIFY_DEVICE_DATA structure?

[monoscout999]

It´s seem a big Struct there, i have no experience on that, but maybe this would help you

[benners]

Thanks Yashied, I have just started using some of the functions in your UDF and replacing my code with them. I have a question about the _WinAPI_CopyFileEx. The file copy fails if the directory is not present in the destination. I have looked through the help and the links on MSDN and cannot see a requirement to create the dir before hand. Is this what needs to be done?

If I manually create the dir before hand the copy works but if not it fails. Bit of a pain when you have a load of files to copy.

Thanks

[Zedna]

_WinAPI_PathFindFileName($sPath) -- > there is x64 bug:

return type should be ptr and not int

Local $Ret = DllCall('shlwapi.dll', 'int', 'PathFindFileNameW', 'ptr', DllStructGetPtr($tData))

Local $Ret = DllCall('shlwapi.dll', 'ptr', 'PathFindFileNameW', 'ptr', DllStructGetPtr($tData))

Edited August 8, 2011 by Zedna