Microsoft operating environments are very dependant on the performance of the graphics card for overall system performance and your graphics card will actually have more determination over the performance than anything you will probably do. However here are a couple of the more obvious pieces of advice:-
1) Make all calculations Integer using % and explicitly declare them.
2) Limit use of arrays and definitaly don't use RE-DIM.
3) Don't use Procedure / Function calls in time critical sections.
4) Use Local Variables if possible.
I am sure there are more and I remember articles on the Microsoft web site on these issues (I have been using VB since Rev 1 and have forgotten more than I would like)..
How do you decide how long something takes ?
1) Create a form
2) Attach some code to it e.g.
3) Time it
Sub Form_MouseDown (Button As Integer, Shift As Integer, X As Single, Y As Single)
For I = 1 To 1000000
Picture1.Line (0, 0)-(1000, 1000)
The example assumes that you have a FORM with a PICTURE control and that there is some room around the PICTURE control.
Click on the form and it will perform 1 millon line draw operations. As there are no variable or calculations involved this is about as quick as you are going to get for line drawing operations.
Run the code and click on the FORM, two times should print out. I get about 71,000 line draw operations per second using VB3 on a 450Mhz Windows 2000 P.C.
I live in hope of a fix for Labview internal temperature reference access.
Driver Rev 5.08 to ???