LabVIEW
RemWireLooseEnds
Solved!
If you have this:
And you press Ctrl-B, you get this:
But if instead if pressing Ctrl-B, you execute , you get this:
Gaaa! I need to remove all broken wires (not just "loose" wires), but apparently such a method doesn't exist.
Be careful though.
If you use OwningVI to get from your diagram to a VI reference, you must close this VI reference!
OwningVI will create a new reference, and it will leak if you don't close it. It will as always close when the top level VI stops...
Search LabVIEW like a graph! 
@paul_a_cardinale wrote:
wiebe@CARYA wrote:
Be careful though.
If you use OwningVI to get from your diagram to a VI reference, you must close this VI reference!
OwningVI will create a new reference, and it will leak if you don't close it. It will as always close when the top level VI stops...
I think the same is true for a reference to any object other than a GObject.
Could be. But in the GObject hierarchy, there aren't that many (if any?) other than the OwningVI.
OwningVI seems especially easy to overlook. Maybe because it's the property of a GObject, and GObjects don't need to be closed.
@paul_a_cardinale wrote:
I think the same is true for a reference to any object other than a GObject.
I would rather say any object other than a Generic.
@raphschru wrote:
@paul_a_cardinale wrote:
I think the same is true for a reference to any object other than a GObject.I would rather say any object other than a Generic.
Even if the object is an integer? Close the integer?
wiebe@CARYA wrote:
@raphschru wrote:
@paul_a_cardinale wrote:
I think the same is true for a reference to any object other than a GObject.I would rather say any object other than a Generic.
Even if the object is an integer? Close the integer?
Well, we were implicitly talking about VI Server references of course.
So any VI Server reference which does not belong to the Generic hierarchy must be closed.
References that belong to the Generic hierarchy do not need to be closed.
@raphschru wrote:
wiebe@CARYA wrote:
@raphschru wrote:
@paul_a_cardinale wrote:
I think the same is true for a reference to any object other than a GObject.I would rather say any object other than a Generic.
Even if the object is an integer? Close the integer?
Well, we were implicitly talking about VI Server references of course.
So any VI Server reference which does not belong to the Generic hierarchy must be closed.
References that belong to the Generic hierarchy do not need to be closed.
But then it's just what Paul said?
@paul_a_cardinale wrote:
I think the same is true for a reference to any object other than a GObject.
"Generic" and "GObject" are not the same, the first is the parent class of the second:
I just said his affirmation can be applied to one level higher in the VI Server hierarchy.
