Quote:
Originally Posted by hamidxa
Root,
I investigated what you were talking about more thoroughly and Im sure of it that you're confusing one task manager for the other.
Look for yourself.
Here is what happens when I map taskmgr to my long talk key and open it up:
As you can see, it consumes a mere 152K, that's it.
What you are confusing it for is this OTHER task manager,
That one consume over 1MB, look:
They are 2 COMPLETELY different and distinct task managers that have nothing to do with one another.
The icons even appear different, and the path is completely different.
My method recommended on the previous page doesn't consume 1MB, it only consumes ~ 150K-170K
Oh, and the CPU usage is only ~ 1% (it only spiked up during the screenshot, then went back to throttling between 0 and 1%)
Also, I personally found quickmenu to be a bit on the cumbersome side and unfortunately not very finger friendly. It almost demands the use of the stylus in some scenarios.
taskmgr is perfect for quick task switching, app killing, and it once more consumes little more than 150K. |
I understand that there are two different taskmanager options in WM.
Will check to see if your option consumes less ram when mapped.
If you just open it then it does take up a lot more resources.
Maybe when it is mapped it works different.
I do know the difference in the two task manager options though, just to be clear.
Also if you ever open the registry editor you will see the exact same task manager options as you are talking about.
Well, you will see processes and CPU Usage as well there.