I'd like to see the implementation of an "AlwaysFalse" key for making our own cleaners in winapp2.ini. Basically what it would do is always have such cleaners with "AlwaysFalse" as the default setting to automatically get disabled/unticked when restarting CCleaner.
Example:
[some App (Logs)*]
LangSecRef=3024
Detect=HKCU\Software\Some App
Default=AlwaysFalse
FileKey1=%appdata%\Some App\Logs|*.*
I support this! I think we mentioned a while back a "one time on" default.
That is already taken into consideration.
Simply omit the "Default" keyword.
Leaving out the default defaults it to false (expected) but selecting it in CCleaner sets an =true that persists.
I second this, too.
Could you provide more details please? I would like to know what advantage this would be. Or perhaps see an example. I am trying to get an idea of what you are talking about.
Thanks!
Default=False
You have to tick that entry first time you run CCleaner, and doesn't get unticked after closing/restarting CCleaner.
Default=AlwaysFalse
Entry resets to false/unticked everytime CCleaner is closed/restared.
Did this help? At least that's how I understood it.
Yes, that helps. Thanks!
Just wondering now though, what kind of custom cleaner he means? For instance, using Win-Rar, you can make silent SFX packages to delete directories or files....
naw, by "custom cleaner" he means win*2.ini entries
Exactly!!! Plus it could also help out Piriform themselves to have some cleaners always disabled on startup, things like the MS AntiMalware cleaner, Office cleaners, etc.