This topic give you access to an AutoIt functions library I maintain which is called PAL, Peter's AutoIt Library. The latest version 1.19 contains 194 functions divided into these topics:
window and screen mouse and GUI GUI controls logics and mathematics string, xml string and file string dialogues and progress bars data lists: lists, stacks, shift registers and key maps (a.ka. dictionaries) miscellaneous: logging/debugging, process and system info A lot of these functions were created in the development of Peace, Peter's Equalizer APO Configuration Extension, which is a user interface for the system-wide audio driver called Equalizer APO.
is it possible to make a wall chams in rainbow six siege using autoit scripts? tell me please and how .
Hi, I am using excel as input media for my program. The excel file (i tried with .xls, .xlsx and .xlsm format) has inputs which the autoit script reads during the run and performs few calculations. Some times (not always), after the run, when i try to open the excel file manually, the file doesnt open at all in excel. see the screenshot attached. However, if the execute the autoit script, the scripts still reads the existing data from that excel and performs the calcs. I copied the excel file to another computer and there too, it doesnt open. So, after this, i cannot edit the excel forever (if i need to change any inputs). It is only this particular file that got affected. other excel files works normal. What could be the problem here. please help as this is a new challenge for me during my program development.
I'm using AutoIt for several years now and I really get the hang of it!
I'm quite the curious OCD perfectionist kind of guy, so I can't help wondering..
what would be the best way to program stuff for the compiler / interpreter / scripting engine?
We're talking about the inner workings of the AutoIt's core here, and how to give it as less friction as possible but also take care of the machine running the script.
Imagine a script where we would constantly have to assign a Boolean value to a variable:
; A: local $bool = false $bool = true $bool = true $bool = false ; B: local $bool = false check(true) check(true) check(false) func check($b) if $bool = $b then return $bool = $b endfunc In this case, would it be better to just overwrite (A) the variable or first check if we really need to (B)?
What would be best for the computers memory if it had to do this for a year non stop?
Another example, imagine you're writing a function with an if statement.
If you would look under the hood of AutoIt, what would be the best way to give your computer as less work / code nesting stack filling as possible:
; A: func decide($b_Input) if $b_Input then ;do something else ;do something else endif endfunc ; B: func decide($b_Input) if $b_Input then ;do something return endif ;do something else endfunc Last one for now:
; A: while 1 ; do stuff wend ; B: while true ; do stuff wend Isn't AutoIt taking an extra step in converting 1 to a Boolean in example (A)?
Or is it the other way around and does the (B) way make AutoIt first convert a keyword (true or false) to a numerical value (0 or 1).
I think this kinda detail stuff is quite interesting, makes me wonder how AutoIt converts and runs our code.
What are your opinions on this topic?
Any coders who know more about the inner workings of AutoIt?
Any people like me who ask themselves similar questions (with examples)?
Let me know! 😉