LabVIEW
Retrieve all names of objects from Strict Type Def
@FrankRalphBob wrote:
Thanks all for your help. It appears I cannot pull a reference off a string typedef, I need to make a control from the strict typedef and then I can pull a reference.
Well, you can do that. But it's probably not what you want. You can use the type def path to open a VI reference. Then get all controls from it's front panel (it's an array with a reference to the string), and follow the same steps as a normal control.
The type def itself does not contain any useful data (except the default values). So it's not very likely to serve any real purpose, except when scripting stuff.
Search LabVIEW like a graph!
@Yamaeda wrote:
If the cluster has many large arrays even that it slow and a DVR will be much faster. 🙂
I use my own .ini file library and it works with string. So it's not very fast. But if it's fast enough, it's fast enough. .vim's will change the way these "general libraries" will be made. They will greatly reduce the need for variants and string conversion.
DVR's can be very fast. However, there a pain to debug, since they are closed when the top-level hierarchy VI stops running. From a programming point of view they're pretty neat. When developing, they're a pain. Up to now I refactored all of them out. My old ideas for making them persistent didn't make it. People need to read more of those ideas...
