[Greg McKaskle]

After a bit of testing, here is my observation.

The big lag is not caused by any specific window ordering, but occurs when the dashboard computer cannot keep up with the cRIO. If you time the rate at which the cRIO sends the images and modify things like which windows are open and which windows are updating, you can sometimes cause the PC to process the images more slowly than they are being sent.

When more images are coming in than are being processed, the excess quickly creates a delay between real world and what you see on the screen. When the buffer is full, the images are dropped, and you will also see some jumpiness as some images are missing.

At this point, I'm still diagnosing the sorts of things that can contribute to this to see what we should change, but in general, if you have your dev environment, dashboard, and driver station all on a single computer, say a small laptop, this may happen sometimes. From what I've seen, minimizing the dev windows is often enough to correct it, and when you aren't running the dev tools at all, it will be even less of an issue.

Greg McKaksle