05-10-2012 08:27 AM
The Get VI Dependencies method I mentioned above returns both the dependency names and the dependency paths. It also gives you good control over what a "dependency" means, which is why the previous properties were deprecated.
08-08-2012 04:12 AM
Can someone explain what is a "Standard VI" and a "Generic VI" as refered to in this "Get VI Dependencies" invoke node?
Thanks in advance.
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
08-10-2012 07:57 AM
Standard VIs are just that - a VI (or subVI, depending on your point of view). It is not a global, control, polymorphic or generic VI. A generic VI is a very buggy internal feature that may or may not ever make it out the door. However, it is another VI type, so is covered by the method. It is very similar to a standard VI.
08-10-2012 08:41 AM
Right so I guess it doesn't change much if I include generic VIs or not since anyway my project don't have any of these.
Thanks for explaining!
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
08-10-2012 10:55 AM
Here's what I came up with : a VI that looks through a project and highlights deprecated property nodes (sorry for the huge BD) :
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
08-13-2012 09:11 AM
just posted this : Find deprecated nodes
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus