Wait a minute - you're generating 3,600 images in order to display a tachometer ?!?
A tacho gives a quick indication of the reading so shouldn't need to be that precise. Insert a numeric readout to give the exact value if necessary.
I doubt that there would be very much difference at all between successive images at such small increments. Even say 360 or maybe 180 images would be smooth and accurate enough for just about any purpose.
And check your math - wouldn't 0.01 degree resolution require 36,000 images ? Maybe you meant 0.1 degree increments ?
I just think that you are on the entirely wrong track.
If you aren't happy with images at say 1 degree steps then a basic alternative would be to use trig functions to calculate the needle end points from the angle and just draw them as lines. If this isn't fancy enough then write a more complex drawing function using maybe circle endpoints. For a relatively small number of pixels, using anti-alias and per pixel colour calculation could make it even prettier.
Programming anything significant is a balancing act of features / programming effort / CPU time / memory / disk tradeoff and I think you're searching around at the extreme end of just one of those dimensions.
A tacho gives a quick indication of the reading so shouldn't need to be that precise. Insert a numeric readout to give the exact value if necessary.
I doubt that there would be very much difference at all between successive images at such small increments. Even say 360 or maybe 180 images would be smooth and accurate enough for just about any purpose.
And check your math - wouldn't 0.01 degree resolution require 36,000 images ? Maybe you meant 0.1 degree increments ?
I just think that you are on the entirely wrong track.
If you aren't happy with images at say 1 degree steps then a basic alternative would be to use trig functions to calculate the needle end points from the angle and just draw them as lines. If this isn't fancy enough then write a more complex drawing function using maybe circle endpoints. For a relatively small number of pixels, using anti-alias and per pixel colour calculation could make it even prettier.
Programming anything significant is a balancing act of features / programming effort / CPU time / memory / disk tradeoff and I think you're searching around at the extreme end of just one of those dimensions.