Add support for using the property node in LVOOP

[tst]

The property node has two major advantage over LVOOP - it allows placing a lot of function calls in a horizontally limited space and it uses text, which is MUCH clearer than small icons (IMO) for something like this. It would be nice if LVOOP had support for this as well.

The implementation I'm thinking of is basically having VIs which will be marked as property VIs (similar to what XControls have) and will only be allowed to have a single input (or output) other than the class and error I/O. These will appear in the list when you connect an LVOOP object to a property node (ideally with the properties from the parents as well), somewhat like this:

When you run the code in this image, LV will run the VIs sequentially, passing the object and error I/O from one VI to the next.

I know that NI already tried to do this in the past, but didn't finish it. Hopefully, enough support here will encourage them to pick it up again.

[RavensFan]

Changing plot settings on a graph.  First you have to write a value to the ActivePlot property to select which plot number you want to act on.  Then you can write to whichever property nodes you want to change for that plot.  You can move onto other plots in the same property node block by writing another number to the ActivePlot property and writing to other properties below that.

[RavensFan]

This duplicated my post for some reason.

Message Edited by Ravens Fan on 08-12-2009 10:15 PM

[Intaris]

This works fine as it stands but will not work if the order of execution is not defined.

[tst]

The others gave an example where the order matters (I've done that too many times) and I can answer "Really?  I didn't know that.  I haven't seen it in documentation or discussed anywhere" with "well, did you try looking in the help for, say, I don't know, the property node, maybe?". It is quite explicit - "The node executes from top to bottom."

😉

[JCC_(SK)]

Do you want replace bundle/unbundle by property node?

Or do you want change Class private data by property node out of the Class VI methods?

Note: We could replace Cluster bundle/unbundle by property node

[tst]

I think the original post explains this well enough - you add "property VIs" to the class and these VIs will be accessible as "properties" in the property node.

Anyway, as you can see, it's in beta, and since you can expect the next version of LV to come out at NIWeek, which is in just over a month, now it's too late to change anything about the feature even if you want to. You can have a look at the actual feature when LV 2010 is released and then give feedback if you don't like it.

[Laura F.]

Available in NI LabVIEW 2010