I agree that a shift register would be more readable than local variables, but I am not sure it would work in my case. To give you a more complete picture of the section of my code that is relevant. There are two parallel while loops that affect this xy chart. They cannot be combined since one needs to execute much faster than the other. One while loops is used mainly to control a number of radio buttons, depending on which button is pressed, the chart will show completely different data, there are a total of 4 places the xy chart can be changed in this while loop, however they are in parallel in a case structure, so they could be controlled with a shift register. The other while loop contains an event structure that in turn contains the main program, and the final result of the program outputs to the xy chart. There are two seperate events that can change values displayed on the xy chart: one is by changing the numeric control for the diameter of the circle, and the other occurs when the main program is complete, all the values on the xy are updated. I understand how to use a shift register if the chart was only being updated in a single while loop, but I dont believe that solution can be implemented with parallel while loops, for the reason that the shift registers would be carrying different values forward. As a worst case solution, I could try to seperate the circle plot from the others, and have a local variable that remembers all three of the others, but like you said, this is not very readable.
Using Labview 7 Express