LabVIEW
Building a text file into an exe (not the support directory)
@BertMcMahan wrote:
That indeed is the way I've done it in the past. I have a global variable I use that I set up during edit time and never write to at run time, then if my ini files don't see the value they check the global. My struggle was that I was hoping to be able to pile all of my default values up into a config file instead of storing them as default values inside a global.
That's why I made an OO config file library. Actually, one of my child classes gets default values from an ini file (, by just extending 1 VI, but that's just bragging).
Search LabVIEW like a graph! 
I'd love to hear more about that- I've been using the To XML functions to do something similar (hence my other thread where you were helping- thanks again by the way).
Does your library use a big batch of commonly used config objects, each making their own ini strings with their own methods, or are you doing something else? I'd wanted to avoid making individual "get ini strings" methods and was hoping to circumvent the issue with XML flattening things, but that seems to be generating more issues than it's worth 🙂
At the moment there is indeed a polymorphic vi, wrapping common type VIs. Arrays of less common types are handled through a variant.
This will be replaced by a .vim at some point, but I'm stuck at lv13 for now...
Why is this bad? As long as it's in the library, you don't have to make it anymore?
You wouldn't have to make an overwrite for each type, in fact you can't (dynamic dispatched VIs are not allowed in a polymorphic VI,IIRC). You'd only have to implement one low level VI...
