>They take comparatively little as far as ongoing resource utilization, especially when compared to the alternative, polling. There's a Class somewhere in the Files Section that provides an API-based timer class, which uses the Win32 API to implement similar functionality; while I suspect that the native Timer also uses the API to implement the function, I can't swear by it.


I've been assuming that a Timer sets some kind of interrupt that fires after the elapsed interval. Therefore no processor usage until the interrupt fires. Can anyone verify this?

Peter Robinson