Comparison of references failed

[P@Anand]

---

@parthabe wrote:

Can you post a snapshot of what you mean? I still dont understand where the Index property available for any control/indicator. 

---

With pleasure. (Sorry, just now checked that its not available in LV2011)

[parthabe]

This is LV 2012 SP1. Have you enabled VI Scripting? 

[P@Anand]

No. Actually I am using LabVIEW 2013. I guess its a new addition to this version.

[JÞB]

---

P@Anand wrote:

No. Actually I am using LabVIEW 2013. I guess its a new addition to this version.

---

Don't guess P

Won't help the OP in 2011

[gerh]

Thanks for all Your help. It's great to have a community like this.

Sorry, I've forgotten to explain my concern about the labels. You need to know this software runs in a laboratory with Labview installed on each computer. So it runs as uncompiled code to control a test stand. If something goes wrong with the experiment usually somebody of the lab personal looks into the code to find out what went wrong. So anything is open to edit by a person without Labview experience.

This can become a serious problem. Recently that caused another institute on our university to throw out Labview from their lab. They do now everything with C.

@Jeff·Þ·Bohrer: Thanks for the flowers .

I know, case 3) was a bad choice because it shares only one VI - I took it as simplest case. There are other cases with more complex code. They share events for many button controls except a small difference for one button. The comparison identifies this difference.

Finally I've pimped the code with many red colored comments.

[parthabe]

May I know which university you work for or belong to?

[gerh]

---

@parthabe wrote:

May I know which university you work for or belong to?

---

Yes, it's the University of Innsbruck.

Edit: I prefer Labview before C. But there are different opinions ...

In concrete there went a longterm experiment wrong which was verry expensive to set up. But that's a different story which doesn't belong to this thread.

[JÞB]

---

@gerh wrote:

Thanks for all Your help. It's great to have a community like this.

Sorry, I've forgotten to explain my concern about the labels. You need to know this software runs in a laboratory with Labview installed on each computer. So it runs as uncompiled code to control a test stand. If something goes wrong with the experiment usually somebody of the lab personal looks into the code to find out what went wrong. So anything is open to edit by a person without Labview experience.

Finally I've pimped the code with many red colored comments.

---

OUCH!  Keep a copy safe under source code control.  Someone will fail to read your comments someday.  But I belive you've done what you can to save the user from themself.  An upgrade to a bug free version of LabVIEW should be available just before judgement day.

[LabBEAN]

Over here Steven H. posted the attached VI for comparing references when the Equal? function was failing to properly equate strict vs. non-strict references to the same control.  I don't have anything earlier than LV 2013 SP1 installed to see whether it would have helped here.  I'm guessing that Jeff was referring to that thread earlier, but maybe it's of some value to have the VI posted both places.

[gerh]

Thanks for the idea, I've just tested it.

The "Compare References.vi" fails in this case. Anyway, there is no comparison between strict and non-strict control references.