Lately I've been working on some user interface improvements. One of these is the addition of a new upper tab, 'Active processes'. In this view the user sees only processes that are actively using the system CPU(s). Basic information about each process is shown in a listview, and a nifty bar graph is used to depict the CPU utilization of each process. These bar graphs make it easy to quickly visualize how available CPU time is being allocated.
Processes in this new listview have the same context menu as those in the traditional 'All processes' view. Multi-select is also supported. Furthermore, double clicking a process in the 'Active processes' listview will automatically select and display the corresponding process the the 'All processes' listview.
How many CPU cycles does this new capability eat? Not as many as you'd expect. First, if the view isn't open, no additional CPU cycles are used. When it is open, it really performs quite well. In most cases, you'll not see ProcessLasso.exe's CPU utilization increase any perceptible amount. When the code has been fully optimized, you'll see even less of an impact on CPU utilization.
As I write this, I'm releasing an early alpha build, v3.79.1. Please keep in mind that this is an early alpha version, so bugs may exist. I am still working out kinks and may change the implementation method before all is said and done. That said, this new feature should work fine for most people, and the rest of the product should be as stable as ever. Enjoy ;).
Processes in this new listview have the same context menu as those in the traditional 'All processes' view. Multi-select is also supported. Furthermore, double clicking a process in the 'Active processes' listview will automatically select and display the corresponding process the the 'All processes' listview.
How many CPU cycles does this new capability eat? Not as many as you'd expect. First, if the view isn't open, no additional CPU cycles are used. When it is open, it really performs quite well. In most cases, you'll not see ProcessLasso.exe's CPU utilization increase any perceptible amount. When the code has been fully optimized, you'll see even less of an impact on CPU utilization.
As I write this, I'm releasing an early alpha build, v3.79.1. Please keep in mind that this is an early alpha version, so bugs may exist. I am still working out kinks and may change the implementation method before all is said and done. That said, this new feature should work fine for most people, and the rest of the product should be as stable as ever. Enjoy ;).
