On Wed, Oct 12, 2005 at 10:28:24PM +0200, Nicolas George wrote: ... > So timeouts that try to catch up are not an absolute necessity, but they are > quite useful in some programs. I think you already know it's very easy enough to make a "timeouts that try to catch up". what's more difficult is making one that saves the api user any time or trouble. you've already given a pretty good example of how to deal with this problem properly. something like: use the timeout to fetch the real system time once every 999/1000's of a second. imho, there's not enough complexity added to make hiding it in an api worthwhile. - Ben _______________________________________________ gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
