An application that I have written must currently be restarted to load its updated configuration (just like LabVIEW.ini). However, I want to change this to have Active settings that can be edited and updated at run-time. Doing some reading lead me to this Managing Application Settings and Options in LabVIEW Applications - Options Dialog Framework (ODF).
Copying directly from this page
" There are quite a few different implementations of an Active Settings component in use in the LabVIEW community today, each offering different advantages and drawbacks, partially based on the personal preference of individual developers. These implementations include:"
- Global variable
- Individual settings
- All settings in a cluster
- Functional Global Variable (FGV)
- LVOOP Class
- Shift Register
- Settings cluster
- Shared Variables
I currently have all of my settings stored in a LVOOP Class. I'm thinking about having a Settings Dialog which allows users to change individual settings and then when close is clicked, it overwrites the current binary file and pushes the updates to a global variable. Anywhere the settings are used, they can read from the global variable and use the accessors of the class to get the settings.
I want to find out more about these implementations before I try and implement one of them. Does anybody have any advice to offer?