@samo79 Yes, Samir but you know how I don't like to write doc and how bad is my english. Even to write my own program's docs annoys me, therefore AmiDock one...
But of course, if somebody wants to write a little documentation, I will include it in the archive with great pleasure.
( I don't know why but I'm sure that I will have no reply ;) )
Yes i know .. but you did it already --> that 2 lines you wrote in the message above are more than enough, just include them on your next dockies's readme
Before CPUDock I used CPUInfo.docky, but it seems that there's a significant difference between those two. When my computer is idle the CPUInfo.docky gives a percentance of 5-8% of CPU, while at the same time CPUDock gives more than 30%!
Which is the most accurate then?
To Be A True Adventurer, You Ought To Play Real Text Adventures
I see, but now another weird thing happens. When I try to right click on the main amidock to edit it I got a Guru Meditation always. That's not very convinient.
To Be A True Adventurer, You Ought To Play Real Text Adventures
I thought of that (taking a grabshot from my camera) as after the DSI error I couldn't do anything, just to move the mouse pointer around and that's all.
Either way, don't ask me, I managed to remove the old CPUInfo.docky and everything seems fine right now. If it will happens again, I will snap a grab, but as I said, I cannot enter the crashlog as nothing is working after the DSI error.
To Be A True Adventurer, You Ought To Play Real Text Adventures
Actually no. Don't ask me, but after multiple resets etc, I managed to right-click on the main docky and remove the CPUInfo.docky completely. I didn't get that weird GM error. :/
Either way, I've seen that you have also some nice docks for time/date and language selector (is that your programs not uploaded on OS4Depot)? Could you share those as well? Thanks.
To Be A True Adventurer, You Ought To Play Real Text Adventures