Actplot property node

[Dawei]

I am using "Property Node" to make some of my input data visible and in-visible in the waveform chart.

I have 13 inputs for now and the number is still increasing.

The type of sink to the "Actplot" is "integer".

In order to set different cases, which I have 4, I have to set 52 property node to make it possible.

Can anyone give me any suggestion for better way to do that?

52 is not much, just too crazy....

[jasonhill]

Put your booleans in an array and stick the property nodes in a for loop.

[edit: forgot to attach image / example]

Message Edited by jasonhill on 12-08-2005 02:51 PM

Message Edited by jasonhill on 12-08-2005 02:51 PM

[Dawei]

What if cases are not just that simple.

For example, 4/13 are visible, 9/13 are invisible.

Is there anyway I can send a message as " [0 1 2 3 4 5 6 7 8 9 10 11 12 ] [T F T F T T T F F T F T F] " to the property node ?

[jasonhill]

This is the neat thing about using the index on the for loop.  As long as your booleans are in order in the array, each iteration of the for loop will index the array, check the boolean value at that index, and perform acordingly.

[T F T F T T T F F T F T F] would turn on 0,2,4,5,6,9,11 and the rest would be off.

[Dawei]

Thanks a lot.

Your advisement is very useful.

Dave  

[chilly_charly]

An alternative solution could be to use a listbox and to show/hide the plots according to the selection.
See the attached vi.

[jasonhill]

I am here for the stars. to help. 

[jasonhill]

I like that idea a lot.  List boxes seem like a more intuative UI interface than a bunch of boolean switches.

I get the following warning when I load in 8.0

"Display plot.vi
    - You will no longer recieve mouse up events after a drag and drop operation.  You will recieve the Drag Ended event for the drag source control instead."

I think that has something to do with the event structure, but not sure what the implications are.

[Dawei]

Thank you, chilly charly.

I had something similar with that before, but yours is defintely much better than mine.

All I need this time is setting up 4 cases.

Maybe the first one is make 0,1 2 visible.

Secind is 3,4,5 visible ... etc.

But I do want to learn how you make that one.

Thanks for your effort again.

[jasonhill]

I suspect that this can be done quite elegantly with an event structure, but I do not understand them well enough to set it up.  If you could set one up to detect when a slider is moved and capture where it is moved from and where it is moved too, you could use a loop like the one attached.  One loop to turn off the three you are moving from and one loop to turn on the three you moved to.