Ok, I'm trying to get my head around timing and keeping an even framerate, and I'm more than a little confused.
The way I see it, you create a timer with CreateTimer(x), where X is the FPS you require.
Then, you can either use WaitEvent or WaitTimer to check the timer. If you use Waitevent, your program can still receive events until the end of the frame. If you use WaitTimer, all activities cease until the next frame.
But, as the docs say: "You should never use the WaitTimer AND WaitEvent methods of controlling speed at the same time, as you will 'lose' ticks."
So which is the best system? Presumably, WaitTimer is best for games and WaitEvent best for GUI stuff?
So where does Vwait come into things? Is Vwait purely to stop your graphics being updated mid-screen?
The way I see it, you create a timer with CreateTimer(x), where X is the FPS you require.
Then, you can either use WaitEvent or WaitTimer to check the timer. If you use Waitevent, your program can still receive events until the end of the frame. If you use WaitTimer, all activities cease until the next frame.
But, as the docs say: "You should never use the WaitTimer AND WaitEvent methods of controlling speed at the same time, as you will 'lose' ticks."
So which is the best system? Presumably, WaitTimer is best for games and WaitEvent best for GUI stuff?
So where does Vwait come into things? Is Vwait purely to stop your graphics being updated mid-screen?