I have couple of scroll bars in my VI. It's big, and it does many things, millions of things, and well does.A big program that is. However I when I needed to add couple of scrollbars it just SLOWS EVERYTHING miserably. And my CORE 2 Duo loaded FULL just because of couple of scroll bars! I don't understand why slide bars in Labview are that SLOW? What's wrong with it? This is just an example of my code, in attachment. It is placed inside the loop. And the iteration of loop is set by a 100ms timer. But when I enable peace of this code, it BARELY does two executions in a second. When I disable it does about 10 executions just as intended, although the rest part of the code is bazillion times bigger and complex. Any clue?? Or replacements??

LabVIEW

slide bars slow EVERYTHING, I dont understand!!!!!

Author

Yes, there are a lot pf problems with the current (unmodified) code, but I don't understand the original problem of slowness. On my 4 year old Laptop (core2duo) I can easily reach a loop rate of <50ms, so maybe something else is wrong on your machine.

Actually thank you for letting me know, It made me a bit astounded and urged me to investigate. Indeed, there was an outdated video driver. Although I ran recently quake 3 with a decent quality it seemed to work fine in 3D, but not in 2D, so I was late to find that oute. After updating I got drammatical boost in the speed of redrawing. So far so good, yet I still found it creepy with these bars. Then I actually replaced them with the boolean array custom pipes, and thats quite a funny thing to look at Still it was little choky, and I experimented with synch-dysplay. It made it more stable but lowered the cycles significantly. And then again I found a little lag when it gets to the stack of 1st and 2nd bars, these two bars, they were simply overlapping just a little, but nevertheless proved too to be ruining all the performance. Then I placed just about 1mm gap in between, and then miracle had happened, it finally ran at a stable rate.Thanks everyone for helping me in this thread, and I will attach the current version, with that cute thing and fixed bugs: