Custom Query (3931 matches)

Hi! In addition to @OSVersion, let's call it for example @WinLevel What's the difference. @OSVersion returns _string_ value like 'WIN_XP', 'WIN_10' and so on. In some cases this is rather not convenient. I'd like to suggest a macro returning _integer_ result to simplify native numeric comparison of OS versions. For example:

@WIN_XP     ->  @WinLevel = 0x0501
@WIN_2003   ->  @WinLevel = 0x0502
@WIN_Vista  ->  @WinLevel = 0x0600
@WIN_7      ->  @WinLevel = 0x0601
@WIN_8      ->  @WinLevel = 0x0602
@WIN_81     ->  @WinLevel = 0x0603
@WIN_10     ->  @WinLevel = 0x0A00

… and so on; in addition the codes above correlate with results returned by WinAPI

The similar codes may be used for server editions especially if there's no difference either it's server or it's ordinary PC Thank you for attention! PS1 May be better @OSLevel instead of @WinLevel?… PS2 As usual sorry for my weak English

While ​_WinAPI_ExpandEnvironmentStrings supports whole strings (but requires an include), ​EnvGet only allows to input a specific environment variable and even then without percents.

I don't presume to retroactively change that, but what about accepting a secondary optional parameter called $full? That is, Func EnvGet($envvariable, $full=False) whereas $full is optional and by default False.

But if $full is True then just do something like (only internally):

If $Full Then
  return Execute("'" & StringRegExpReplace($envvariable, "%(\w+)%",  "' & EnvGet('$1') & '" ) & "'")
EndIf

This will allow to support commands like ConsoleWrite(EnvGet("My temp variables are %temp% and %tmp%", true)).

Please add _WinAPI_OpenEvent function that allows to check global events from windows.

_WinAPI_CreateEvent function by documentation should allow to open events, but if global event was created using different application, then script won't be able to access it.

Function in windows: ​https://learn.microsoft.com/en-us/windows/win32/api/synchapi/nf-synchapi-createeventa?redirectedfrom=MSDN&f1url=%3FappId%3DDev10IDEF1%26l%3DEN-US%26k%3Dk(CreateEvent)%3Bk(DevLang-C)%3Bk(TargetOS-WINDOWS)%26rd%3Dtrue

Function written in AutoIT which works in my case (Maybe positions of parameters could be changed like in already written AutoIT functions, to keep same structure in all AutoIT functions):

Func _WinAPI_OpenEvent($sName = "", $dwDesiredAccess = 0x1F0003 , $bInheritHandle = True)
	If $sName = "" Then $sName = Null

	Local $aCall = DllCall("kernel32.dll", "handle", "OpenEventW", "struct*", $dwDesiredAccess, "bool", $bInheritHandle, _
			"wstr", $sName)
	If @error Then Return SetError(@error, @extended, 0)

	Local $iLastError = _WinAPI_GetLastError()
	If $iLastError Then Return SetExtended($iLastError, 0)

	Return $aCall[0]
EndFunc   ;==>_WinAPI_OpenEvent

If this function can be added, then it would make sense to add it to documentation as well like in here : ​https://www.autoitscript.com/autoit3/docs/libfunctions/_WinAPI_CreateEvent.htm