I agree, it sounds like your panel is consuming all the resources it is given. All of the suggestions given so far are good ones, but you might also find it useful to be more systematic about speeding it up and trying them out. Clone your application so that you can instrument it to measure various parts or delete and hide things to find the slower components. One of the first things to do is to make it easy and efficient to run and rerun your app. If it controls something, you likely want to disconnect it and maybe emulate your I/O. When you have a good loop rate, start removing things from the loop looking for large jumps. By subtracting them, you can get a feel for what is insignificant and what is big. As mentioned, it may simply be that a control is overlapped or has anti-aliased line drawing turned on.
If you have other questions after making some measurements, ask again. Also, if you would like, you can submit this for our NIWeek session where a couple of us will examine and possibly improve apps for clarity, correctness, or performance. The app will be anonymous by the time it is presented at NIWeek. Just email it, or portions of it to [EMAIL PROTECTED] Greg McKaskle
