Root > Customizing EurekaLog > EurekaLog options > Dynamic options > Variables


Previous pageReturn to chapter overviewNext page   

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.


Important Notes:

Some variables (such as %APPDATA%, %TEMP% folders, etc.) are specific to user account. E.g. each user account has its own %APPDATA% folder. EurekaLog will use %APPDATA% folder of user running your executable. For example:

If you are writing a Win32 Service application - such application is run by "Local System" account by default. "Local System" account has its own %APPDATA% folder, for example: "C:\WINDOWS\system32\config\systemprofile\AppData" or "C:\WINDOWS\SysWOW64\config\systemprofile\AppData" (depending on bitness of your application and operating system).
If you are writing a low integrity application (such as ISAPI DLL running by IIS) - such applications are very restricted. Low-integrity APPDATA folder (%FOLDERID_LocalAppDataLow%) should be used: C:\Users\UserName\AppData\LocalLow\Neos Eureka S.r.l\EurekaLog\Bug Reports\your-executable\


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:



"Variables" dialog


"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:

1. Open "Variables" window.
2. Select variable that you want to use.
3. Click "Copy" (or double-click variable). Dialog will be closed.
4. Paste variable name from clipboard (Ctrl + V or Shift + Ins) to target setting's edit box.



This dialog suggests you only build-in special pseudo-variables (those with names started with "_") and commonly used variables. However, you can use any environment variable (even if it's not listed in this dialog).
You can also use relative file paths. For example, any path which starts with . (dot) will be relative to your current executable (regardless of actual current folder, which may be changed, say, by system open dialog). For example, ".\BugReport.el" means file in the same folder as your executable.


See more:


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.



See also:

Send feedback... Build date: 2022-03-28
Last edited: 2022-01-13
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: