BB "Debug" mode?
How about some mode which outputs to a text file, what BB did, where and when? Also maybe create a list, as text, of the directories/folders where it found and deleted data, so testers can confirm if any additional files or data there was missed for deletion?
Just a thought...
ROCKNROLLKID
Sun, 09/14/2014 - 20:22
Permalink
This would be a nice feature
This would be a nice feature and would probably help finding some bugs in BleachBit, but should be a seperate installation for it meaning a totally different download for BleachBit Debug mode on the download page.
____________________
Also known as Alex.
Moderator for BleachBit and a maintainer for Winapp2.
Check out my open-source group on Steam: http://steamcommunity.com/groups/opencommunity
Windows 10 x64 (switching to ReactOS in the future).
andrew
Sun, 09/14/2014 - 20:28
Permalink
I like the debug mode idea.
I like the debug mode idea. How about enabling debug mode by adding a command line option, holding a key while starting BleachBit, or as a separate menu item in the operating system?
Also, debug mode could be started part way through a session through an option in the BleachBit menu.
Finally, I would like to set this up to stop BleachBit on Windows from logging crashes to c:\program files\. This is an automatic feature from py2exe, a software used by BleachBit on Windows.
---
Andrew, lead developer
ROCKNROLLKID
Wed, 09/17/2014 - 20:33
Permalink
I recommended BleachBit to
I recommended BleachBit to use a seperate installation so the main BleachBit program would not have to increase in size when it is not needed, especially when BleachBit size is something that needs to be reduced. I know in Flash Player, the debugger is about 1MB bigger then the regular one (that is for there standalone edition). That is just my opinion, though.
____________________
Also known as Alex.
Moderator for BleachBit and a maintainer for Winapp2.
Check out my open-source group on Steam: http://steamcommunity.com/groups/opencommunity
Windows 10 x64 (switching to ReactOS in the future).
andrew
Wed, 09/17/2014 - 21:01
Permalink
It's good to be vigilant
It's good to be vigilant about the size. In this case, it would be a pretty small difference (<100KB) in size to simply log common events.
In addition to the regular logging, also adding the unit tests (self tests) would add maybe 200KB.
---
Andrew, lead developer