os4 cpu metter ?

@Capehill

RC2 solves the crash/DSI problem. THX

@kas1e

Yes, the Busy mode is known to be "incompatible" with CPU dockies that also busy loop. CW measures the idle time (which no other tasks used) by busy looping and apparently CPU dockies do the same so they start racing and both use 50% of the CPU. However, the Simple mode should help with that because it sleeps rather that runs.

I will add the menu and iconify gadget at some point.

@Raziel

Try cloning and building https://github.com/capehill/tequila

It can probably show which task is using the CPU.

@Capehill

...nevermind...

Bult it, let it ran and then run cpuwatcher.
UUno task is eating away more than 71%...i guess that is a task from cpuwatcher?

@Capehill

Confirmed if I change in cpu.docky (no option, just changing code and recompile) to use simple_mode instead of busy_mode I get "normal" cpu % values.

@Raziel

Yes. It seems that you are interested in the task that uses the remaining 20-30 %. Of course you can run also Tequila without CPU Watcher and then the most intensive task should be on the top of list.

@Capehill

I did, the task that eats away most of the the cpu is idle.task.
Nothing else.

Once cpuwatcher starts UUno is the one

RC3 is released: https://github.com/capehill/cpuwatcher/releases/tag/v0.7-rc3

Changes:
- Use window class
- Add menus
- Add iconification
- Add About window

@Capehill

Everything works, just when you iconify it, the icon position is wrong
Btw, if you add locale support we can translate it aswell

ah cool haven't logged in a ahile and nice to see an updated CPU docky! will try it out on my X1000 later today

thanks Capehill!

@samo79

I might implement locale support in the future. Need to study the topic a bit.

EDIT:

http://os4depot.net/?function=showfil ... /workbench/cpuwatcher.lha