How to pass a graph to another vi without stripping off the properties????

[Clueless1]

Would it be too hard to do this?

[smercurio_fc]

What do you mean by "pass a graph". Are you referring to the data or to the actual graph indicator? For the latter you need to pass a control reference.

[Ray.R]

... and for the data, you would just wire... the data (array). 🙂

Both are relatively simple.

What smercurio proposes would retain (most?/all?) the properties of the graph.  Are you using cursor lines, etc?

Message Edited by JoeLabView on 03-12-2008 05:20 PM

[Clueless1]

I want to be able to have a vi (MYxyGraph.vi) that takes data and all of the other information that makes an xy graph meaningful and produces a graph indicator that incorporates all of that data (metadata IS data -- legends, colors,titles,patterns, etc...).  I would like to for that indicator to get returned as an output argument of MYxyGraph.vi.

What do I have to do that will get me close to this use case?

Thanks


Message Edited by Clueless1 on 03-12-2008 04:27 PM

Message Edited by Clueless1 on 03-12-2008 04:28 PM

[smercurio_fc]

Like I said, a control reference as an output would give you this. However, my guess is that you want to apply this to a higher level VI that has a graph, and are assuming that you can just copy the graph onto this graph in a higher level VI. If this is the case what you actually should do is to create a VI that has a graph control reference as an input. You pass it the control reference of the graph in your higher level VI, and let the subVI set all the properties programmatically.

[Clueless1]

OK, I think i get it. 

Thanks

[Ray.R]

Additionally to what Mr. smercurio stated, you can wire the reference from the original graph to property nodes in the sub-vi to "extract" the property information.

The property node from the "Application Controls" of the Functions palette.

[Clueless1]

I guess it's like having to malloc a struct before writing  data to it.   All front panel objects must be allocated in the vi that owns the front panel and they only exist in that panel.  Objects that are "passed" as indicators(outputs) of the parent into the control (input) of the subvi(child)  are  not pointers but cause a memcopy into a new instance of the object.  Yes/No?????

[Ray.R]

are you referring to the reference & property node?  I tend to think more as objects...  or in the ms world... active-x objects...

Remember that objects can have methods and properties. Where properties are the attributes of an object (size, color, value, visibility, etc).

[Clueless1]

I'm using the term object here more in the generic sense of something (cluster,variable,array,waveformGraph, etc ...) that, once instantiated, occupies a chunk of memory (either stack or heap I don't know)  until it is released either explicitly, or by the underlying architecture of labview.  I'm just trying to get a peek behind the curtain in order to better understand how LV wants me to program (wire?) it.