In our first hour
of today’s AutoHotkey webinar we talked about working with multiple scripts in AutoHotkey. How you can break out functions into separate files and leverage the library.
In the Second Hour we did Q&A and discussed other things we typically automate.
The two scripts we highlighted were: Dictionary by Fanatic Guru and iThesauras based of Dictionary by rommmecek.
Working with Multiple Files in AHK
- Breaking out scripts into separate files / functions (Here is a page several videos on functions)
- Using #include
- Lib folder
- Sharing data between scripts via:
- Passing via command line parameters
- OnMessage
- COM object via Windows Temp Environment variables
- COM object via custom object
- Consolidating scripts from multiple files into one
Libraries and #Includes
- A script may call a function in an external file without having to use #Include. For this to work, a file of the same name as the function must exist in one of the following library directories:
- Local library: %A_ScriptDir%\Lib\
- User library: %A_MyDocuments%\AutoHotkey\Lib\
- Standard library: path-to-the-currently-running-AutoHotkey.exe\Lib\
Order of search
- Original file
- Local Library
- User Library
- Standard Library
- If a function is not found, but has an underscore in the name, it will search for a library with everything up to the underscore. (E.g. If your function is named “IE_Load” it will search for a file named IE.ahk and load it)
Benefits of using Library: 1) Code maintenance, 2) Fewer files to keep track of, etc. 3) Easier to read code
Negatives of using Library: Sharing code can be a bit more complex
Sharing data between scripts: Command line Parameters
AutoHotkey.exe [Switches] [Script Filename] [Script Parameters]
CompiledScript.exe [Switches] [Script Parameters]
Script Parameters:
- The string(s) you want to pass into the script, with each separated from the next by a space.
- Any parameter that contains spaces should be enclosed in quotation marks.
- The script sees incoming parameters as the variables %1%, %2%, and so on.
- In addition, %0% contains the number of parameters passed (0 if none). However, these variables cannot be referenced directly in an expression because they would be seen as numbers rather than variables.
- In the receiver, use Param2 = %2% ;Note NO colon
Pros: Simple, reliable
Cons: Only works when starting up, One-direction, Only passes strings/variables
Sharing data between scripts: OnMessage
Pass String between scripts with OnMessage
Pros: Simple to Use
Cons: Code is somewhat complex, A bit resource intensive, Pass single variable
Sharing data between scripts: Temp Environment Variable
Create a Temporary Environment Variable and stores it, until reboot, in Registery under: HKCU\VolatileEnvironment
Pros: Easy to use, Variable is Accessible after “sender” exits, Fast, Can use objects / dot-notation
Cons: Pass variables/strings, Character limitation
Sharing data between scripts: Custom COM Object
Registers a unique CLSID (Computer Licence Security ID) in registry (A CLSID is a globally unique identifier that identifies a COM class object. If your server or container allows linking to its embedded objects, you need to register a CLSID for each supported class of objects.)
Pros:Can pass objects, Functions, Variables,Strings, Bi-directional, Super Fast
Cons: Code is more complex, Can’t use FOR loops to iterate over Objects, Can slow some when passing large data
Consolidating Multiple Scripts into One
- AutoExec section – (Top of script until first: Return, Exit, hotkey/hotstring label)
- Hotkeys – Conflicting Hotkeys prevents script from running (Make them context sensitive?)
- Hotstrings – First Hotstring takes presedent
- Re-using: Variables , Functions, Labels, Classes cause errors
- Duplicate code – Often bring in things multiple times
- Reasons why prefer one over the other
- Multiple scripts-
- Sharing scripts is easier
- Troubleshooting can be easier
- One Script-
- One file to edit
- One script in system tray (Can use #Notrayicon in multiple scritps to help negate this)
- Ease sharing of code
