Interesting idea.
I was looking through the documentation and backend.ini and the following thoughts occurred:
I use a set up that aspires to be portable and one of the things I do is to launch PStart from a batch file after booting. The batch file sets some environment variables which then become available to programs I launch via PStart (and I launch FARR from PStart, so FARR gets them too as well as programs launched from FARR).
One of the environment variables I set is called DRIVE and it's set up in the batch file as:
and subsequent environment variables refer to DRIVE. I also have an environment variable named PAR (for portable applications root), which is set as:
In backend.ini I notice you have:
as well as:
I didn't read backend's source, but if it doesn't already, do you think it might be useful for it to handle environment variables? My recent thinking is that file and folder path information stored by programs being wired to absolute (or even relative, though that seems a bit nicer) paths is an unhappy situation waiting to happen -- and I've been thinking that environment variable support for such things might lead to happier results.
What do you think?
backend1.zip
Logged
