Make Path element accept %VARIABLES%
Expected Behavior
- [ ] When adding an environment variable name %COMPUTERNAME% -
- [ ] When adding a built-in Autohotkey variable name %A_ComputerName% -
... into a path it ends up with the value filled in in the a2 runtime.
Do we need both? Are there conflicts?
I implemented a helper function ExpandPathPlaceholders.
This allows ahk modules to expand a predefined set of A_ variables and all environmental variables.
I believe this solves this issue. Do you agree, @ewerybody ?
Hmm I dunno. I still think that this has some value for the Path Element. We could actually have a module relative variable with the module name or such.
I think that is up for the module dev to define. it isn't needed in most cases.
I for example have created static properties of the module's class with the moduleName and modulePath
related: #120
Ok. This should also be available for hotkeys. With preselection help menu.