Custom Query (3922 matches)

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)).

Hello,

In my company we have a lot (around 100-150) of AutoIt programs of various size. So first: thank you for your great language!!!

We have a script to compile all our programs. We run it several times a day. We have tried to speed up the compilation duration by calling AutoItWrapper.exe multiple times (in parallel), in order to benefit from all the CPU cores on our server.

However that caused us big troubles. For example, some executables were mixed or swapped (i.e. programA.exe and programB.exe are both the executable file for programA.au3, and the code in programB.au3 is compiled nowhere).

To reproduce, just try to Run() 3 or 4 AutoItWrapper.exe programs in parallel.

Could you please try to solve this issue, as it would really improve our compilation time ? Thank you!!!!

Expand the advanced window descriptor to use X, Y, W, H for match criteria. Example usage:

ControlClick($hWnd, "", "[CLASS:BUTTON]; X:10; Y:10; W:50; H:25")

Which would search for a button at position 10,10 with a width of 50 and height of 25. Unspecified parameters should be ignored.