Hide indicator will not pass a value to another vi

[Joseph_Loo]

I have a vi that I do not want the people to see or manipulate. On the front pannel I select hide indicator. When I run the application, it loads the local variables up and pass it to another vi. When the indicator is hidden, no data is passed. When I unhide the indicator, the value is passed. When I try to trace the hidden variable, it will sometimes be set properly.

Is there a limitation when you set indicators to hide?

[altenbach]

What is your LabVIEW version?

[Joseph_Loo]

I found the problem. It was an operator error. It seems that a loop was being executed at the wrong time.

[mission_labview]

hi

I have encountered the same problem and labview version is LABVIEW 7.1 any ideas?????

[Joseph_Loo]

I am running labview 7.1.1. I found out the problem accidentally. When I was doing the original testing, it had the sympon that whenever I hide the variable, it would show blank. When I showed the variable, it would show up properly.

I suggest, the place where you actually set the value you place a unique value to it. That way, when the value gets change, you have an idea where it was set. I also used a lot of local variables of the hidden indicator or control within the loop. I generally keep the terminal outside of the loops.

[Dennis_Knutson]

Mission:

If you are actually updating an indicator in a subVI and you acutally have it wired to the control panel, the value will always be passed to the main. If you can post an example that demonstrates where it doesn't, I think everyone would love to see it.

Joseph:

It sounds like you are using local variables inappropriately. Why would you put the terminal outside the loop and write to a local variable inside?

[Joseph_Loo]

I am setting the variables at different places at different times. Outside of the loop when you want to initialize the value and inside the loop when you need to change the value. You could use shift registers, but the number of lines start getting really bad. since it has to go through multiple case structures at different location. I just think sometimes it is easier to just set the local variables. Plus in general it is pretty easy to find the location using the find command.

[Dennis_Knutson]

Easier doesn't mean better. Local variables create copies of data and can cause race conditions. If you find you have more than a one or two shift registers, you can use the bundle/unbundle by name on multiple lines and use a single shift register.

[Joseph_Loo]

In my particuliar needs, there are no race conditions. It is to supply information for display or print out.

[mission_labview]

Hi Dennis

I ll surely post the example where it is not happening.

I am actually passing the cluster output from a subvi where I am then passing the value to an indicator.I am taking a local variable of that indicator and passing it to the second frame of the sequence.

Now when I hide the indicator the problem arrives.

I hope I am making sense to you.

anyways I ll post a demo vi soon.

regards