Digital Display(s) of a Graph - Programmatically hide individually

[Broken_Arrow]

I have a Graph tracking 15 things. The graph can have the entire Digital Display "array" on or off, but I haven't found a particular Property Node for to access these displays  individually. I have been able to do this by clicking on one of the displays, then creating a Property Node. Odd thing is, said Property Node has no Label, no identifier whatsoever. This could get messy - making my own labels. It also seems slow.  However, this method does "work". I haven't made an exe to test it "compiled". Any experience with this? Advice? There should be a better way.

Message Edited by Broken Arrow on 08-06-2005 02:22 PM

Message Edited by Broken Arrow on 08-06-2005 02:22 PM

[SG_ENGINEER]

Hi

I am assuming you are passing an array to the graph. I think one way is the pass the 15 individual data each into a case structure. you can then flip a switch to decide if the data or null passes through this case structure. you can combine them together again before passing to the graph indicator. there could be a more elegant method. but i think this one should work fine. you end up with 15 toggle switch. kinda cool actually. haha

Goy

[tst]

3 points:

First, are you sure you mean a graph and not a chart? In my LV 7.0 only charts have digital displays (which makes sense, because graphs don't have a current value).

Second, it is possible to create references to objects which are not "exposed" (which is the reason it doesn't have a name) and these work fine, even in built EXEs. You can see it's not exposed by right clicking the property node and going to Link To. You will see that the object is not in the list.

Third, why do you say you can't manipulate the array? If you create a property node for the chart and select the Digital Display[] property, you get an array of references to the digital displays. Isn't that exactly what you want?

[Broken_Arrow]

It IS a Chart and not a Graph, correct. My mistake.
Speaking of the Property Node to get the references to the individual Digital Displays: Yes, I noticed that, but quite frankly, I'm not sure what to do with the references. I've never used references (except by explicit example), and don't fully understand them. I've always been able to do what I wanted with Property Nodes, Invoke Nodes, and Local Variables. What exactly am I missing out on?
For now, I'm using the no-name Property Nodes that I pop off the individual Digital Displays, and that's working OK, but slow.
If the referennces can be used somehow, I'd love to see it. Sorry if it's LabVIEW 101

[tst]

A reference is a "pointer" to a LV object (an application, a VI, a control, a piece of a control...). When you right click a control and select Create>>Property Node it creates an explicitly linked node. That is, a node which is always connected to that specific object. If you select the property node from the Application Control palette you will see it has a reference input. You can wire a reference to any object into it, and the properties available will change based on which class the reference you wire into it belongs to. By not using this you are missing out on many of the dynamic features of LV. Have a look at this [broken link removed] tutorial for some more explanations.

As for this specific thing, if you select the property I mentioned, which is an array of references for the displays, and wire it into a for loop, you will get in the for loop a reference for each of the displays. If you wire this into a property node (the one from the App Control palette), you will be able to control all of them in the loop. The loop will simply iterate through the array.

[Broken_Arrow]

Very well explained, thanks! The loop, array, etc all make perfect since - been doing that for 4 years, just never with References.