Invisible wrote:
> I believe the problem is that the library won't let me specify an 
> absolute time, only relative times. So if I was "wait 100 ms", but the 
> other processing that the program does takes 1 ms, the delay ends up 
> being 101 ms, not 100 ms.

Well, yeah.

> Still, since no other API is available, there's not much I can do about 
> it. (Other than whinge at the developers and see if it gets fixed in the 
> next release of the library...)

No, you do your processing, then you look at the highest resolution clock 
you have and figure out how much *longer* you have to wait, then you wait. 
Adjusting for the length of time it takes to figure out how much longer you 
have to wait.

-- 
Darren New, San Diego CA, USA (PST)
    Eiffel - The language that lets you specify exactly
    that the code does what you think it does, even if
    it doesn't do what you wanted.

Post a reply to this message