How do I programmatically change the plot legend names on my xy graph?

[cderrico]

PAY ATTENTION!!

The properties of Settings are NO PARALLEL! They are sequencial!

They will be executed in seqeunce.

I attach 2 examples:

• The first is KO -> You we'll experience an error!
• The second OK -> No Error

In my opinion this is a bug.

For now this is the correct solution.

Ciao!

Carmine

[UliB]

Hello Carmine.

---

@cderrico wrote:

In my opinion this is a bug.

---

This is not a bug. This is expected behavior. The help for property node clearly states: 'The node executes from top to bottom.'

How would you handle something like the attached picture in parallel?

 

UliB

[cderrico]

Thank you for your answer!

Your example is so clear, in no way it can bring us to a not wished situation.

For example in my real time application I need to customize the name of graph-lines.

In this case (please see my examples) you can have e total wrong name configuration.

From a function that i call, the expected behaviour is that it wait for all input and set it all together with priority for "ActPlot" number.

If you have a complex software this behaviour can conduct you to lose so many times.

Thank you for your attention!
Carmine

[NickG_LMCO]

What about multiple graph lines... Plot 1, Plot 2, Plot 3.... is it really just the first name element? or can I get to the other plot name labels too?

[RavensFan]

You're replying into a 2 year old thread and your questions aren't clear as to what message you are referring to.

What specifically do you mean by "first name element"?

If you are having an issue with your VI, it would be best if you create a new message thread and include your VI along with an explanation as to where you are having problems.

[NickG_LMCO]

I figured it out.  ActPlot was the key.

[EngineerThis!]

I had a question typed here but then realized I was being dumb. I resolved it but couldn't delete my comment. 

[RTSLVU]

My plot labels are read from a text file during initialization and put in a string array.

Then I do this:

It's a "strict" property node because it's in a sub-vi and a uses a reference