| Details: |
- XNodes are specified with the naming convention: ";Dxxx.vi" where xxx is any text.
- XNodes, when in memory either running or not, do not appear in the VI Hierarchy.
- XNodes are executed by dragging them from the palette or from a file browser onto the Block Diagram.
- When XNodes are on the Block Diagram, their code cannot be edited (similar to a running reentrant VI).
- XNodes are not reentrant VIs, but they can have multiple instances in parallel.
- XNodes are EVENT DRIVEN VIs; they only execute and make a single pass through each time an event occurs.
- You can easily freeze your system if you have any code that freezes or does not stop polling in an event execution.
- You can easily crash your system if you incorrectly specify your terminals.
- You can easily create internal code that becomes impossible to execute, this makes any VI containing the XNode to fail to run.
- If you do not return the right parameters at the right events, the XNode can cease to function and instead show up as a subVI.
- XNodes do not show their front panels ever, but removing the front panel can cause system instability.
- I found all this with the State Diagram Toolkit for LabVIEW 7.1, at C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\addons\statediagram\;DNI_IntToEnum.vi
|
|---|
XNodes