JavaJack,

I've managed to replicate this now. I'll see if I can find a way to bring it down to nothing. Somehow I think it's still doing graphic updates when it shouldn't be.

-William

hhoffmann,

I think I have a fix for the scrollbar issue which will be in the next release. I haven't been able to replicate the problem of setting the time to 00:00:00 - which ever way I try it, it works but I'm not going to look into this any further because Atomic Timer can't be used as a clock anyway - after it's been running for a day it would show the number of days it had been running for - that isn't what you want, you need to use Atomic Clock instead.

-William

hhoffmann,

I have a Widget called "Atomic Clock" published which will do the clock thing much better than Atomic Timer. I'll look into why it crashed when you set the timer to 0:0:0 though.

Someone else has reported the help scrollbar thing to me on another Widget. There's a bug in Konfabulator which causes scrollbars not to appear under certain conditions - there's a workaround to it which I've implemented but that doesn't seem to work on some computers. I'll see if I can work out why and fix it in the next release.

My CPU is a P4 Mobile (slightly older than the now common 4M) 2.2ghz.
Using process explorer I drilled down into the threads for that process, and it's konfabulator.exe thread that's eating the CPU, not gdi or kernel. In case it matters, this is on Konfabulator 2.1.1.

1. help file displays one page only, no scrolling down possible
(therefore I do not know what to expect, what the settings mean, whether 24 hour format possible, ...)
2. the first thing I tried is setting the target time to 0:0:0 - this crashed the widget
(idea was to simply use the timer as a clock)