two indicators of only one variable

[Mathan]

here its in 8.0 that will open in 8.2

[Norbert_B]

Etay,

in LV, one does not "define" controls and indicators, one "creates" them. They are the graphical representation of the value which is to be passed on the appropriate wire. So the sentence "the wire is the variable" is correct. Just as Ben wrote, think of indicators as "printf" and controls as "scanf".

---

etay23 wrote:
[...]i don't want to go over all the program and connect 'same numeric' indicator to it.

I just want to see it's display in both places on the fron panel.[...]

---

I don't get the reason for this. I can only think of a single example where it is recommended/mandatory that the same value is displayed more than once at a time. So if you are using something like a tab control and want to display a certain value on two of three pages, this request makes sense. If you don't have such an approach, adding new indicators distracts the user and makes the application bad in regard of handling.

hope this helps,

Norbert 

Message Edited by Norbert B on 03-10-2009 03:35 AM

[etay23]

Hello Norbert,

you are right about the terminology! the right term is creats, i understand that.

I also understand perfecly the idea of control as "scanf" and indicator as "printf".

You are right  on guessing my problem with the tab control, is there an elegant solution for that?

regards,

etay

[Norbert_B]

Etay,

in this case, i suggest to use a shiftregister in order to keep the value of the wire in your application. The main reason is that in many applications, the display of tab controls is managed using a case structure. Therefore each case could have their own (matching) controls and indicators.

See attached example for a possible guideline.

hope this helps,

Norbert 

[Norbert_B]

Well, i have to add that, despite my post, my example does not use a shiftregister. I have done this in the first place since the source (input control) is generating data as fast as the data is displayed. This is possibly not very clever, esp. if acquisition takes some time. Then maybe you want to store values until they change. THIS can be done with shiftregisters very easily.

hope this helps,

Norbert