From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
09-12-2007 06:51 AM
I saw that... 🙂 LOL!!
We'll converse off-line 😉
04-15-2008 12:08 PM
07-29-2008 04:23 AM
Hi,
I have made a strict type def, which is a text ring. I open the VI reference -> get Panel property node -> Controls[] -> Index first element (there is only one, the ring) -> change Strings and values, and then close reference.
If I call this subvi from a VI, which includes this strict type ring, it will be only updated, when I restart the VI. And not in runtime. I don´t get any error, everything looks fine, but the strings and values are not updated 😞
Is there a way not to restart the VI, but to modify the ring programatically?
regards
MB
07-29-2008 04:51 AM - edited 07-29-2008 05:00 AM
11-24-2009 08:04 AM - edited 11-24-2009 08:06 AM
This posting is intended to update this Nugget to highlight the new functionality available in LV 2009 that lets us group libraries in the VI Hierarchy screen.
The following tow images show...
The Hierarchy of a small app without grouping of libraries. AS you can see the DAQ functions (DAQ in header) are scattered on the screen.
By grouping the VIs by library and colapsing the other libraries,
we can see how the DAQ functions are structured to the point where we can almost make an educated guess that maybe "AI Control" is an Action Engine used by "AI Stop", "AI Read" and "AI init" .... maybe
Have fun,
Ben
09-28-2010 10:42 AM
For those of you that have read through this entire thread Kudos to you!
If you are using LV 2010 or better then you will find your reward for your reading in this thread where Darren tells us how we can use the new option that lets us view clustrers as an icon to avoid teh "Diagram Explosion" issue when editing a type definition.
Enjoy!
Ben