Perhaps we can have multiple levels of "WINAPP2.INI". What I mean by this is keep the current embedding as-is. Then we have the WINAPP2.INI "generated" by us forum users. Then have a WINAPP3.INI and a WINAPP4.INI file.. CC would first go to its internal definitions, then simplye work through all the external WINAPP(X) files it finds.
This way we get the best of what the user community generates, and we can keep our custom entries totally separate and safe throughout upgrades to both CC's main program and the forum's WINAPP2.INI ..
Why can't you just add your customs to the community generated file on your PC? More files to check longer it takes for CCleaner to open and load/detect programs. More Files, more chance for ccleaner to mess up. More Files More bloat. More files more to go through every CCleaner update for removal of now embedded.
That said, the developers read all threads and take into consideration all suggestions.
Why can't you just add your customs to the community generated file on your PC? More files to check longer it takes for CCleaner to open and load/detect programs. More Files, more chance for ccleaner to mess up. More Files More bloat. More files more to go through every CCleaner update for removal of now embedded.
That said, the developers read all threads and take into consideration all suggestions.
Yes, that is what I do nowadays. When I grab the community generated .ini I copy my custom additions from the old one and add it into the new community one.
I was looking for a way to keep the community updates separate from mine. But, nonetheless, it is still a workable solution.
Interesting request which has made me think it would be much better implemented in the ccleaner.ini file under a heading such as:
[Winapp2.ini]
Of course that would mean having to enable the ccleaner.ini file for the settings instead.
That way you could have your own user made/custom winapp2 cleaners right inside the settings file ccleaner.ini which wouldn't be touched by the community version, that would be allot cleaner and you wouldn't need a bunch of winapp#.ini files.