There is no better way to avoid those pesky globals than the good old uninitialized shift register. There is, however, a better name. We like to call them "functional globals" these days. It souds better than the old name, "LabVIEW 2 style global".
In fact, the method is a sort of stepping stone to GOOP (Graphical Object Oriented Programming). You can think of your functional global subVI as a data object with read and write methods. Sometimes I like to include an Init case as well. For configuration data, you can build Save and Load cases in which you can put more subVIs to read and write INI files and such.
So, if someone out there thinks of a "better way" I'd love to hear about it too! Until then, I'll keep cranking out my functional globals
.
Daniel L. Press
PrimeTest Corp.
www.primetest.com