LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

labview runs quicker when i click onto the scroll bar

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?

ta.

Message Edited by John Pierson on 10-20-2009 11:20 AM
0 Kudos
Message 21 of 37
(943 Views)
Here LV 8.2 version
Message 22 of 37
(939 Views)

chears.

 

yup i can also confirm with your one, it does run quicker when the mouse holds down the side bar.

Cool!

0 Kudos
Message 23 of 37
(938 Views)
Did anybody try if this exists in LV 2009 also? Maybe a bug... ?! Smiley Indifferent
- Partha ( CLD until Oct 2024 🙂 )
Message 24 of 37
(912 Views)
are we into some cheat code?:smileyvery-happy:
Message 25 of 37
(910 Views)

muks wrote:
are we into some cheat code?:smileyvery-happy:

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, 
UINT msg,
WPARAM wparam,
LPARAM lparam)
{
// this is the main message handler of the system
PAINTSTRUCT ps; // used in WM_PAINT
HDC hdc; // handle to a device context
char buffer[80];// used to print strings
 
// what is the message
switch(msg)
{
case WM_CREATE:
{
// do initialization stuff here
// return success
return(0);
} break;
 
case WM_MOUSEMOVE:
{
//bla bla bla
} break;
 
 
case WM_PAINT:
{
//bla bla bla
} break;
 
case WM_DESTROY:
{


And the messages like

 

WM_LBUTTONDOWN
WM_NCLBUTTONDOWN
WM_TIMER
WM_MOUSEMOVE
WM_HSCROLL
WM_VSCROLL
WM_NCPAINT
WM_PAINT

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).

 

Andrey.

Message 26 of 37
(917 Views)

If you drag windows, many programs pauses (atleast the window refresh), could this happen when clicking the scroll bar, thus shaving the window refresh time?

 

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
Message 27 of 37
(904 Views)

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?

0 Kudos
Message 28 of 37
(890 Views)

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. Smiley Happy

 

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. Smiley Wink

- Partha ( CLD until Oct 2024 🙂 )
0 Kudos
Message 29 of 37
(884 Views)

parthabe wrote:

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! Smiley Mad (it didn't help that the code had 2000+ global variables).

 

 

 

 

 

yes I said 2000+ global variables.

 

Richard






0 Kudos
Message 30 of 37
(880 Views)