Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project and User-Defined Configurations #12

Open
volks73 opened this issue Nov 25, 2019 · 0 comments
Open

Project and User-Defined Configurations #12

volks73 opened this issue Nov 25, 2019 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@volks73
Copy link
Member

volks73 commented Nov 25, 2019

The behavior of various Eulogy-related actions and APIs should be customizable from configuration (INI) files. The order of precedence would be as follows:

  1. System INI file, located in the Toolkit API root folder for a LabVIEW installation, i.e. C:\Program Files (x86)\National Instruments\LabVIEW YYYY\vi.lib\Field R&D Services\Eulogy\Eulogy.ini. This would define the defaults for the behavior, where YYYY is replaced with the year.
  2. User INI file, located in the LabVIEW Data folder for a user, i.e. C:\Users\<username>\Documents\LabVIEW Data\Eulogy\Eulogy.ini. This would define user-specific configurations for Eulogy behavior, where <username> is replaced with the current Windows user.
  3. Project INI file, located in the same folder as the LabVIEW project file (.lvproj), i.e. C:\Users\<username>\Code\<project-name>\Eulogy.ini. This would define configurations for Eulogy behavior specific to the project and/or source code, where <username> is replaced with the current Windows user and <project-name> is replaced with the name of the project. This would allow multiple people working on the same project to have the same Eulogy behavior. The Eulogy.ini file would be included in version control and any source distribution.

Examples of configurations would be the default grave digger and necromancer to use.

@volks73 volks73 added the enhancement New feature or request label Nov 25, 2019
@volks73 volks73 self-assigned this Nov 25, 2019
This was referenced Nov 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant