WinAPIEx UDF

[UEZ]

No, it's there where it was before. Post #1

Sometimes my body is on earth but not my mind

Too much work caused abnormal behavour...

Sorry.

UEZ

[Yashied]

The library has been updated.

v1.9

Added functions

_WinAPI_CharToOem

_WinAPI_CreateFileEx

_WinAPI_EnumProcessThreads

_WinAPI_EnumProcessWindows

_WinAPI_IntersectRect

_WinAPI_IsRectEmpty

_WinAPI_MoveFileEx

_WinAPI_OemToChar

_WinAPI_ShareFolderDlg

_WinAPI_SubtractRect

+ few examples

Edited October 10, 2009 by Yashied

[Yashied]

Changed the library for AutoIt 3.3.1.0 (Beta) and above: _WinAPI_PathFindOnPath() function is disabled.

[Zedna]

I expected your WinAPIEx library will be added in the next beta (3.3.1.2).

That's pity it isn't :-(

[Yashied]

I expected your WinAPIEx library will be added in the next beta (3.3.1.2).

That's pity it isn't :-(

Probably too much work for verification. I will support until in this form. Edited October 15, 2009 by Yashied

[kjcdude]

Ran into a problem after I upgraded to 3.3.1.3.

Get the following error.

C:\Program Files\AutoIt3\Beta\Include\WinAPIEx.au3(5633,53) : WARNING: $tagTEXTMETRIC: possibly used before declaration.
    Local $tTEXTMETRIC = DllStructCreate($tagTEXTMETRIC)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^

Edited October 22, 2009 by kjcdude

[Yashied]

Ran into a problem after I upgraded to 3.3.1.3.

Get the following error.

C:\Program Files\AutoIt3\Beta\Include\WinAPIEx.au3(5633,53) : WARNING: $tagTEXTMETRIC: possibly used before declaration.
    Local $tTEXTMETRIC = DllStructCreate($tagTEXTMETRIC)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^

I do not know why in the latest Beta removed $tagTEXTMETRIC global constant from the StructureConstants.au3. Anyway, I fixed that. See first post.

[Yashied]

Fixed several minor bugs.

[Dolemite50]

Wow,

What an ocean of work. Thanks a lot, Yashied. You've got a ton of good stuff on this site.

I found this script while looking for functions similar to Holger's_MenuIcons. From what I can tell your script provides a more modern approach of accomplishing the same thing. Is that right?

BTW, I think I found an error in the _WinAPI_SHGetFileInfo example. It tries calling itself rather than _WinAPI_ShellGetFileInfo.

For $i = 1 To $Ext[0]
    $tSHFILEINFO = _WinAPI_SHGetFileInfo($Ext[$i],...

Your script is way over my head so I may be wrong. If that's the case feel free to have a good laugh around the water cooler at my expense.

Keep on coding, man! You're on fire!!

[Yashied]

_WinAPI_SHGetFileInfo() is a function name and not file name. Anyway, proof of the code correctness may be that the example of which you say works fine.

[Dolemite50]

Hi Yashied,

I actually had to change it to _WinAPI_ShellGetFileInfo to get it to work. (1.8 I doesn't have "_WinAPI_SHGetFileInfo()")

Anyhow, it worked like a champ, and fast!

BTW, there are a few of us on the board who have been stuck trying to create a multi-state PNG button. Is there a func in this library that might help? Your _SetImage looks really close but I read somewhere that you didn't design it to be dynamic. Is WinApiEX our savior?

Edit: _SetBitmap --> SetImage

Edited October 31, 2009 by Dolemite50

[rajeshontheweb]

hi there, i just noticed i couldnt find SHQueryRecycleBin and SHEmptyRecycleBin wasnt found. can u add them as well..

[jchd]

Hi Yashied,

Thank you for this excellent contribution.

You may want to change the documentation of the function _WinAPI_GetProcAddress($hModule, $sProc).

; Syntax.........: _WinAPI_GetProcAddress ( $hModule, $sProc )

; Parameters.....: $hModule - Handle to the DLL module that contains the function.

; $sProc - The function name.

The description of $hModule is misleading. Feeding a "DLL handle" as returned by DllOpen (as seems implied) won't work.

Local $hDll = DllOpen($sDllFilename)

Local $pFct = _WinAPI_GetProcAddress($hDll, $sProc) <-- failure

Windows GetProcAddress needs an actual _address_ typically obtained by LoadLibrary[W] while AutoIt DllOpen returns an integer handle.

Local $RetVal = DllCall("kernel32.dll", "ptr", "LoadLibraryW", "wstr", $sDllFilename)

Local $pFct = _WinAPI_GetProcAddress($RetVal[0], $sProc)

Also you may want to use LoadLibraryW and wstr just in case there are non-ANSI characters in the path.

[wraithdu]

I disagree. Usage of the windows api and dll calls implies some understanding OF the windows api. That parameter description is directly from MSDN. Instead, the documentation of DllOpen should be more clear that the return value is a pseudo handle (NOT a real handle) that is only to be used with AutoIt internal dll functions, not UDFs.

Edited December 4, 2009 by wraithdu

[jchd]

I disagree. Usage of the windows api and dll calls implies some understanding OF the windows api. That parameter description is directly from MSDN. Instead, the documentation of DllOpen should be more clear that the return value is a pseudo handle (NOT a real handle) that is only to be used with AutoIt internal dll functions, not UDFs.

Of course you're right. The real problem is AutoIt using the term handle for something else.

[Yashied]

Returns a dll "handle" to be used with subsequent Dll functions.

It's OK.

[Yashied]

Now I am preparing an update to version 2.0. If anyone has suggestions, please tell me about it here.

[Yashied]

The library has been updated.

v2.0

Added functions

_WinAPI_AdjustTokenPrivileges

_WinAPI_ColorHLSToRGB

_WinAPI_ColorRGBToHLS

_WinAPI_IsValidLocale

_WinAPI_LoDWord

_WinAPI_LookupPrivilegeName

_WinAPI_LookupPrivilegeValue

_WinAPI_HiDWord

_WinAPI_OpenProcessToken

_WinAPI_RegCloseKey

_WinAPI_RegCopyTree

_WinAPI_RegCreateKey

_WinAPI_RegDeleteEmptyKey

_WinAPI_RegDeleteKey

_WinAPI_RegDeleteTree

_WinAPI_RegEnumKey

_WinAPI_RegEnumValue

_WinAPI_RegFlushKey

_WinAPI_RegisterHotKey

_WinAPI_RegOpenKey

_WinAPI_RegQueryInfoKey

_WinAPI_RegQueryLastWriteTime

_WinAPI_RegQueryValue

_WinAPI_RegRestoreKey

_WinAPI_RegSaveKey

_WinAPI_RegSetValue

_WinAPI_UnionStruct

_WinAPI_UnregisterHotKey

+ few examples

[KaFu]

The library has been updated.

v2.0

Becoming more and more a standard UDF ... thanks for all you efforts m8, party hard !

[Dolemite50]

Nicely done, Yashied! I really appreciate the good examples.