Synaesthesiac

Thank you very much for asking these questions. Incidentally, these are exactly the same questions I had about the CLA Preparation guide. I disagree that not knowing what these terms mean indicates that you are not ready for the CLA exam. I'm sure you can gather what the meaning of the words are, and even what meaning they have in software design. However, these line items are very unclear: 1.) State persistance and restoration of what? The entire application or individual VIs? A "state" could be a state in a state machine, or an abstract application state. 2.) Configuration data could mean a .INI file of config settings. However, if you look through the LabVIEW Advanced coursebook, Configuration refers to architect-level Configuration for other developers, e.g. File Locking, Version Control, Revision and Requirements Tracking, etc. For example, you can modify both your Project as well as individual VIs to handle "Configuration" as it relates to Requirements Tracking, and this is how it is discussed in the coursebook--there's nothing about application configuration using config.ini files. I'm still not sure what they are referring to in the preparation guide. 3.) Why do they refer to scalability and simulation in the same bullet point? Those could be considered completely unrelated, and when they pair them together, it leads me to believe that I should be building a scalabale simulation module. Is that the case? It wouldn't make much sense. So, I think that the fact that you identified these three questions as being confusing among all the others, this may indicate that you are more prepared for the CLA than you think. You are on the level of asking questions about the fine points and discrepencies in the preparation guide, which to me indiciates a high degree of understanding. No stupid questions, just stupid answers, right? QUOTE (RAJKU @ Mar 22 2009, 01:34 PM)

I have created a subVI that creates a new file by copying a template .vit file to a .vi file in a specified folder. I am including this subVI as part of a library, referenced by a .lvlib I have imported in to my project. The original .vit is not referenced by the .lvlib. It appears that the new file is somehow referenced by the .lvlib, and when I attempt to dynamically call the new vi, I get the following error: "You attempted to open a VI Server reference to an out-of-scope VI."... When I locate the new vi, it has a name like the following: Library.lvlib:NewVI.vi Is there a way around this?

Hello all-- I've not even begun to explore the scripting features in LabVIEW, but am wondering if it is possible to write a script that generates a type def consisting of multiple controls (e.g. a type defined cluster of strings, booleans, etc.) and saves it as a .ctl file. What would be really excellent is if I could pass a flattened xml string that defines the controls (in the same format as is outputted from a "flatten to xml" node), and generate a .ctl file from that. If this is possible, I might start to really delve in to LabVIEW scripting