Hey! I loved the previous konfabulator's version. But this one isn't sensitive enough for me, even after configuring it to give me the straight percentage. This one tells me 100% almost all the time. The previous version (which, for some reason I can't see on my desktop when I open it with Kon. v2.1.1) was way better at showing me the exact percentage drop at even 10 feet from my access point. Keep up the good work though and is there any fix for that coming? P.S. I absolutely love the systemDashboard series. By far my favorite!!

Im have a temporary fix ready for submission. It adds a preference that disables the colorization, which is the current cpu hog. Default will leave the colorization on, so you will need to turn it off if the cpu usage is a problem for you. just be sure to turn it back on when the next version of K comes out, as Im pretty sure the issue has just been corrected for the next release of K.

Okay guys, im working on this cpu usage thing... and this is what Ive come up with. It is caused directly by the coorization commands I use to change the colors of the rings based on the signal strength. Now, I may be mistaken, but since the only thing that has changed sinc ethis widget was last updated was the Konfabulator version, im inclined to say that something changed within the commands im calling on the K side. Needless to say, im going to try and track this down. In the mean time, i will probably add a preference to disable the colorization until I can get this resolved.

I am really wondering, how, out of the blue, people are reporting high cpu usage. I cant duplicate these effects on my end, and nothing has changed in months. Those reporting high usage, please let me know what kind of wireless card you are using.

Pretty widget, but eats 20% cpu on my computer also. Roughly once every second and a half, regardless of how the timer is set. I'm Running Windows on a 3.4GHz P4 Laptop.