Why does a control go to zero when clicking outside of it?

[SteveChandler]

it is pretty basic, and there are no variables or property nodes that would force the control.

Does this mean there are no local variables or property nodes at all or just none that you think would force the control? Right click on the control and select find. If there are any local variables you will have the option to find them all. Same for property nodes. If the only thing under find is terminal then you probably did uncover a bug in LabVIEW. But I doubt it.

[vilh0005]

One control has no property nodes, the other does, however it is not set to force a zero.

[billko]

maybe the corresponding event in your event structure doesn't contain the control itself?  this could cause unexpected behavior.

[vilh0005]

I have attached the code (labview 2009.) Forgive the mess, as it is still under dev, but you should get the idea. The two controls of interest are "frequency" and "Kp force"

[vilh0005]

I miswrote about one control have in a property node, it is actually a variable.

[Yamaeda]

Which control/variable is the culprit?

/Y

[vilh0005]

One is labeled as "Frequency" the other is "Kp Force"

[vilh0005]

Both controls were giving problems.

[RavensFan]

Try putting a small wait statment in the while loop that contains those control terminals.  I don't see anthing in that loop that might throttle the speed of that loop.  If it is running as fast as possible, it might be eating up all your CPU cycles.  Considering it is a large front panel with a lot of controls, and some seem to be overlapping (PID control tabs overlap the bigger tab control with the graph), your CPU might be spending all of its time running that loop and updating the front panel that it never has a chance to handle the mouse and keyboard events that trigger the updates of those controls.

[vilh0005]

Loop timing may be a consideration. Total CPU utilization is less that 50% when running. There is a sort of psuedo-wait statement, as the UDP read functions will hold the loop until a new sample is available to read from the target (I need to re-verify this) so the loop runs at about 50 hz in reality.