Hi all,
I am aware that LimpidClock needs a lot of CPU but it surely does not use 10% all the time. It rather sleeps most of the time and wakes up every second to redraw the display. Currently it always redraws the entire window and not only those parts which changed, that's why it needs so much CPU. So it is well possible that it sleeps 9/10ths of a second and then needs 100% CPU for 1/10th of a second. Your measurement tool probably only gives you the average of 10% per second.
Concerning the "my game stops every second" issue, this is easy to solve. There is a config item where you can set the task priority. Just decrease it to below 0 and the problem will go away. The shipped config has a prio of 1 IIRC, so that the clock runs accurate without being stopped by other tasks. If you lower the prio, the other tasks run smooth but LimpidClock's display might be delayed. Especially if you run tasks which use up all CPU (e.g. UAE).
There is a big potential of optimisation in LimpidClock. Up to now the main attention in development was on features. Now it's time to look at speed.
Bye,
Thomas
