- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
What is a "dynamic dependency" ?
Solved!
Little_Owl
08-05-2016 05:07 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi all,
I've been reading white papers about properly managing a Labview code base and I've seen several references to 'dynamic dependencies'. Can someone explain what a dynamic dependency is and provide a simple example? I couldn't find a good explanation on the web or this forum.
Thanks!
Solved! Go to Solution.
Bob_Schor
08-05-2016 05:19 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
A search for "LabVIEW Dynamic Dependency" takes you to one of LabVIEW Project's Help documents. There it explains that a "Dependency" refers to a VI that needs to be in memory when a Caller calls it. If it is called directly by your LabVIEW code (for example, by being placed on a Block Diagram), that is a static dependency because it doesn't change. If, however, you don't declare which VI you want to run until Run Time, and specify it by, say, typing its name into an indicator, that is a dynamic dependency, "dynamic" because it is changable/alterable at run time, and a dependency because it still needs to be in memory in order to run (it's up to you and LabVIEW to make this happen).
Check out the Help document for more explanation.
Bob Schor
08-05-2016 05:39 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
@Bob_Schor wrote:A search for "LabVIEW Dynamic Dependency" takes you to one of LabVIEW Project's Help documents. There it explains that a "Dependency" refers to a VI that needs to be in memory when a Caller calls it. If it is called directly by your LabVIEW code (for example, by being placed on a Block Diagram), that is a static dependency because it doesn't change. If, however, you don't declare which VI you want to run until Run Time, and specify it by, say, typing its name into an indicator, that is a dynamic dependency, "dynamic" because it is changable/alterable at run time, and a dependency because it still needs to be in memory in order to run (it's up to you and LabVIEW to make this happen).
Check out the Help document for more explanation.
Bob Schor
Thanks for the help! Your comparison between a static and dynamic dependency was clearer than the Labview help document.
