> The lazy polling approach I described in my last post to Vojtech> ("block until there's a new readout or N milliseconds have passed,> whichever is later") looks like a more general, accurate and efficient> interface.

That's not good.

If the program says '100ms' because it knows it will need to do a GUI updatethen, and you block it for 5 seconds because that's when the next valueupdate happens, the user is stuck looking at their gkrellm or whatever notdoing anything at all for 4.9 seconds....

This almost forces the use of multiple threads if the program wants to doits own timer management.[unhandled content-type:application/pgp-signature]