> Nothing using any significant amount of CPU. No DAQ hardware. All > the communication is done over one ethernet connection. >
I think what is happening is that you are catching mouse move events. At the moment, the event structure doesn't have a built-in mechanism for collapsing mouse move events, and it will queue all of them the OS hands it. If you do little or no processing for a move event, it isn't a problem. If you spend much time, the queue gets pretty bug pretty fast, then it takes your diagram multiple seconds to process them out of the queue and find the mouse up. If this sounds familiar, you can either process the move events faster, put a limit on which ones you process using the timestamp or distance comparison to the previous one processed, etc. You might even find some devzone VIs that do this for you. Greg McKaskle
