02-26-2007 07:46 PM
02-27-2007
05:06 AM
- last edited on
12-03-2025
02:24 PM
by
Content Cleaner
Note - the error you're getting comes from the Cancel Notification primitive, not from the Release primitive. The reason for this is that once you destroy the notifier its reference no longer points to a valid object and so you get the invalid input error. This is actually something many people use to stop loops - you wire the error terminal into the stop condition and once the notifier\queue\whatever is destroyed the primitive will error and stop the loop.
Using a local to pass the reference is a possibility, but it is a potential for race conditions. If the local was read before the correct value was put into the indicator you would get the error you saw. Wiring is generally prefered in this cases (and in many other cases where you could use locals). In general - wires or synchronization objects should be used to pass data, not locals.
To learn more about LabVIEW, I suggest you try searching this site and google for LabVIEW tutorials. Here, here, here, here and here are a few you can start with and here are some tutorial videos. You can also contact your local NI office and join one of their courses.
In addition, I suggest you read the LabVIEW style guide and the LabVIEW user manual (Help>>Search the LabVIEW Bookshelf).