kgaliano

Thank you for your explanations.

Thank you for your replies.

Thank you for your replies. Does this imply that, in general, "This VI" references do not need to be closed? So I am guessing that memory leaks typically arise from other references (e.g., control refnums, indicators, files, etc.)?

Good afternoon, Some subVI's of the openG package in Labview 2012 use an error guard to enclose their content (i.e., a case structure with an error wire as the boolean input). In some subVI's, in the "No Error" case of the error guard, the error wire is not propagated through (i.e., the code uses a "no error" constant somewhere else to continue the error wire. One example of this is in the subVI of "Get Data Name from TD__ogtk.vi" in version 2012. I know that for most practical applications, this is alright because if there isn't an error input, then a "no error" constant is almost identical to the input. However, I was wondering if there was a way around this for when one manually introduces warnings in one's code (i.e., suppose I have a subVI that checks a condition to introduce a warning to alert the user of a potential problem, and then at some point this error wire goes into Get Data Name from TD__ogtk.vi, wouldn't the warning become lost?). Thank you. Kevin

Good afternoon, I have a question regarding the subVI called "Write Panel to INI__ogtk.vi" in Labview version 2012. It seems like the input parameter "VI ref" is a reference that is not closed by this VI (specifically where the property node used to obtain the VI name is located). I was wondering if this can cause a memory leak? Thank you.