Support Environment variables as root directories
Support Environment variables as root directories
The EVB has an internal set of variables for root folders, such as %Default Folder%, %TEMP Folder%, etc. How about expanding the functionality and adding support for processing arbitrary user and system variables? Some programs access paths written in their own variables, and this data is now impossible to pack with boxed app, if it has custom paths.
Re: Support Environment variables as root directories
Hi, saying truth, I can't imagine the case where such functionality can be required.
In path variables, usually the variable PATH is used, moreover it is used by a system.
Do you have an example, where such feature could be required?
In path variables, usually the variable PATH is used, moreover it is used by a system.
Do you have an example, where such feature could be required?
Re: Support Environment variables as root directories
I apologize for the late reply, there were other things to do.Do you have an example, where such feature could be required?
You are wrong about the rare usage. There are many programs (especially old ones) such as Maya, XSI, Visual Studio, Python, as well as many other specialized programs (SDK, CADs, IDEs) that create external system/user variables to access their files through other programs or parts of their own packages. For example, variables such as %MAYAPLUGINPATH%, %PYTHONHOME%, %VPROJECT%, etc. are used to search for Maya plugins, access to the Python executable environment, or to a game project in the Valve Source SDK. %MSDevDir% or %MSVCDir% are used by old Viaual Studios to access compilers. None of them use %PATH% for this, as it has different purpose.
Therefore, having support for paths wrapped in variables, we could autonomously virtualize a program with part of the files from another program, which accessed by variables only, without installing this secondary program into the system.