[Customdrawn] LazClock exercise

[Felipe Monteiro de Carvalho]

On Mon, Apr 2, 2012 at 9:32 AM, Michael Schnell <mschnell at lumino.de> wrote:
> IMHO: TTimer is specified not to miss an event, unless the main thread is
> busy for at least a complete period.

Missing a clock tick is not related to missing a TTimer event and I
doubt that TTimer events are being lost here. LazClock does not use
TTimer to count time, only to send invalidate requests, it calculates
the time on its own to be precise about what time it really is
regardless of any problems in TTimer. So when it looses a tick it
actually means that since the last paint of the clock there was an
interval of aprox. 2 seconds to the next paint. Of course the interval
should never be that big unless you are running very CPU intersive
programs together with LazClock.


-- 
Felipe Monteiro de Carvalho