Limiting access on remote panels

Question

Since you cannot limit the number of people able to view a remote front panel (I am under the assumption that either everyone can view the panel or no one can), I am trying to come up with a way to only allow one person to control and VIEW the remote panel.  I think it might be possible to create an "access" VI that will redirect a user to the experiment VI if no one else is using it or not allow them to access the experiment VI if someone else is using it at the time.  Is it possible for one remote panel to tell if another remote panel is being accessed, and if so, can a remote panel link you to another remote panel?

Answer 1

The way you have it set up is basically correct, but I'll make some comments before explaining the problem.
First, don't use clusters functions to process arrays. If you want to get the first element of the array, use Index Array (as it is or with a 0 wired into the index input).
Second, maybe it's just me, but I don't like the icon displays for the terminals (takes too much diagram space and doesn't really help). You can switch it with a right click for each terminal or disable it in the options menu competely. On the same note, the wire should continue straight to the Array function, and have an extension going up to the indicator, instead of taking a detour through the indicator. It just looks better and is clearer to read. You really should look at those tutorials and the style guide.
Third, your timeout case isn't necessary. A timeout case should only be used if you have code that you need to execute if no event has occured. You can simply delete the timeout and delete the case. To stop the loop, simply add an event for the stop button and wire T only out of that case. As a side point, there is no point in having a 100 ms wait if you are already waiting the 10 ms of the timeout.
Now, to the problem.
The indicator isn't being updated because the loop isn't running, and the loop isn't running because you wired the stop condition from the top loop into the bottom loop. This means (the biggest rule of dataflow programming) that the top loop will have to complete before that information will be available, which means the bottom loop will only start running after the top loop. To debug and know if your loops are running, create an indicator for the i terminal or use a probe on wires inside the area you need to check.
What you need to do is cut the loops. The easiest way is to place the stop control in the bottom loop and to use a value change event to stop the top loop. If you have more than 2 loops, it's usually easiest to create a local variable (you will need to change the mechanical action for the boolean control).
Once you did this it should work and my quick test (on the same computer) shows that the array is updated as soon as the browser goes to another page.
Try to take over the world!