![]() ![]() The tool uses the original signed ProcessHacker driver so no need to enable test signing, etc. Now some things are not yet done, but being a pre release and a work in progress that is imho Ok. In my use case I have the task manager (now my own before that TaskInfo) always open on a small monitor on the side and can always keep an eye on whats going on on my system. The thread panel contains a stack trace for the selected thread giving even more insight in wat the selected application is doing right now. An other panel shows all open connections/sockets providing also data rate information. The task info panels show all open handles (including file handles), the current file position is one of the columns what is quite useful to see what is a program actually working on right now disk wise. The toolbar provides decently sized graphs providing not just CPU usage but also usage of Objects, handles, network and IO/disk access. ![]() No pressing refresh most data are refreshed continuously. Quick access to information one is interested in is emphasized interesting data are provided in easy to access (as less clicks as possible) panels, with no need to open windows or windows of sub windows. The UI focuses on expedience and getting real time data of what the system is doing at any given moment. The UI layout is inspired by the old tool TaskInfo which unfortunately seams abandoned since 2012 and it being closed source means its dead.įor me personally the UX of TaskInfo always was the best of the best, although growing up with something makes you think this way about many things ant it may not be true, its just the result of getting used to it.īut I think I can make a good case why the particular UX style is objectively good. In case there is someone interested in a new powerful task manager, here is one: it uses the ProcessHacker kernel driver and the phlib as back-end. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |