Environment variables are a set of dynamic named values that can affect the way running processes will behave on a computer. They can be said in some sense to create the operating environment in which a process runs. For example, an environment variable with a standard name can store the location that a particular computer system uses to store temporary files - this may vary from one computer system to another. A process which invokes the environment variable by (standard) name can be sure that it is storing temporary information in a directory that exists and is expected to have sufficient space.
You can use environment variables in any text values in your project settings. You can insert variable by using "Variables" window. Variable is inserted as special tag. When you run your application at run-time, any variable value will be replaced with actual value, which is calculated at run-time.
For example, if you set your folder for saving bug-report to "%APPDATA%\MyBugReports" then your bug reports will be saved to C:\Users\UserName\AppData\Roaming\MyBugReports\ or C:\Documents and Settings\UserName\Application Data\MyBugReports - depending on real value of %APPDATA% variable at run-time.
Note: variables names are case-insensitive.
When you're in your EurekaLog project options (see above), you can click on "Variables" button at dialog's bottom:
"Variables" button in EurekaLog project options
Click on this button and you will see such window:
"Copy" button will close the window with copying selected variable into clipboard. Alternatively: you can just double-click on variable in the list.
"Close" button will close the window without any action.
Suggested action's sequence:
So, while variables is an easy way to add some dynamic behaviour to EurekaLog options, their powers are limited. There may be no variable for your specific need or it may be not applicable to desired options (such as checked/unchecked option kind). In this case - you can set up/alter options from code.