that rules out my computer being the problem.
cool, i thought i was going mad, at least others have this problem.
coudl you do me a favour, could you save that last programme as lv8.2 for me?
yup i can also confirm with your one, it does run quicker when the mouse holds down the side bar.
Yep, "hardware acceleration"
But "if the result is correct, it cannot be a bug." (c) altenbach
In general its just a bit other behavior when messaging queue changed by pressing and holding mouse button.
Somewhere behind of LabVIEW Window should be the code like this:
LRESULT CALLBACK WindowProc(HWND hwnd,
// this is the main message handler of the system
PAINTSTRUCT ps; // used in WM_PAINT
HDC hdc; // handle to a device context
char buffer;// used to print strings
// what is the message
// do initialization stuff here
// return success
//bla bla bla
//bla bla bla
And the messages like
continuously coming into the loop above. Something changed in this queue and this caused timing changes in processing loop - where UI repaint also involved.
In some cases its caused delays in code, but in some cases, as we can see above - speedup.
If you want to go deep into windows messaging queue, then probably you can explore messages with PeekMessageA Win API function, or set up hook for appropriate messages and see what and how changed (both things are very good programming exercises).
that was exactly my thought. but would you gain the same delay from simply minamising the window?
-would that be a good test of the idea?
Minimising the LV windows WILL speed up the execution, I ve seen (realized) it many times in the past. That too after building a big application into an EXE, speed will increase manyfolds.
We did so & suggested our client Principal Test Engineer to keep the ATE UI minimised all the time during production testing, since it was going to generate report on the fly in the behind anyway.
We did so & suggested our client Principal Test Engineer to keep the ATE UI minimised ...
off-topic a bit:
I have hard enough time convincing them not to play Solitaire on the ATE. Seriously, I went on a service call once for a setup where a 20 or so mS delay could mean the difference between $1k of damaged parts or a smooth run (I didn't write the software) and found they were playing on the computer while this thing was processing product! (it didn't help that the code had 2000+ global variables).
yes I said 2000+ global variables.