User defined app paths

It would be really nice if we could edit our own list of application paths.

Then we could simply use e.g. {apppath|exiftool} in all scripts and buttons and need not worry about exiftool's true location or if it's in the path environment.

Switching between installations and using other people's buttons would become easier as well.

1 Like

Seems like something aliases could be used for.

If a required alias is not defined, the script could also prompt the user to locate the needed file/folder and then run a command to create the alias pointing to it.

I'd rather see Opus at the helm here, otherwise we might end up with a bunch of aliases pointing to one app, one for each script author.

That could still happen without a convention on how to name things, which would also work with aliases.

Alternatively, the {apppath|...} code gets its information from HKEY_CLASSES_ROOT\Applications, so a script could add the info there if there's no entry for a program.

A way to make {apppath|...} or similar prompt for the exe and store the path automatically could be cool, though, I agree. That would make it work with non-script buttons that refer to external tools, where it wouldn't be realistic to change aliases or registry data in the command itself.

1 Like