Hello everyone!
In the Process Lasso UI, when right-clicking a process and selecting "Exclude from ProBalance", "ExampleProcess.exe" is added to the ProBalance exclusion list.
However, if "More/Exclude from SmartTrim" is selected, then "Drive:\Path\ExampleProcess.exe" is added to the SmartTrim exclusion list.
Not sure if this is by design, but it feels a bit inconsistent even if it can be quickly edited (if you remember to edit it!). I'd suggest to add the process alone (no path) in both situations. I am guessing using the full path is a less frequent scenario.
Perhaps you could also consider an additional option to simultaneously add a process to both exclusion lists.
Thanks
Good observation! This has been changed as of v15.0.5.3 beta.
We'll also consider a combined option to exclude a process from both those features.
Standardizing both to use just the process name (e.g., ExampleProcess.exe) makes sense for simplicity, especially since full paths are less commonly needed.
Instead of adding directly to the list, right-clicking and selecting any of the "Exclude" options can open a quick, small dialog. This dialog will: Pre-populate `ExampleProcess.exe`. There are checkboxes for "Exclude from ProBalance" and "Exclude from SmartTrim".
This dialog will automatically fill in `ExampleProcess.exe`. It features checkboxes for "Exclude from ProBalance" and "Exclude from SmartTrim".
What are the potential impacts on system performance when processes are excluded from ProBalance and SmartTrim?
Interesting point! Excluding processes from both features offers granular control. But what about situations where the excluded process is legitimately triggering a security concern? Could this create blind spots? Perhaps a whitelisting/blacklisting system within the excluded process category itself would be a good solution, akin to how one might handle levels in Drift Boss. This could add another layer of security.