For restructuring a larger application I created a VI that shall recursively replaces all missing VIs and type defs based on a lookup table.
For VIs this works fine but it does not work with missing *.ctl files (type def) for controls or constants because there is no "MissingTypeDef" property available.
I'd like to suggest to add something a "MissingXYName" property to each class type that refers to a file - corresponding to what the VI class is already offering.
In my personal opinion it would be even better to have a file-pathname property (which shall be valid even if the file is missing) plus a second property (enum) that shows if this file is valid or not (0: all fine; 1: there but somehow invalid; 2: missing).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Already available with the 'Missing Dependency Names' and 'Missing Dependency Paths' properties of the GObject class in LabVIEW 2015 and later.