[Customdrawn] LazClock exercise

[Giuliano Colla]

Il 02/04/2012 09:37, Felipe Monteiro de Carvalho ha scritto:
> 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.
The problems appears to be not that TTimer events are lost, but that 
TTimer events aren't generated.
See the Cronometer test.
>   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.
>
There was no other running application. Just normal background Desktop 
related activities.
I managed to make it skip a second just moving the mouse over the form, 
and thus generating many mousemove events, which apparently do keep the 
main loop too busy. We need to investigate further.