Allow eventual starting a new track log file

What steps will reproduce the problem?
1.
2.
3.

What is expected? What do you get instead?
It would be great to allow starting a new track log file (with new name) using 
some reasonable policy, something like these:
a) start a new track log file every time the program is started unconditionally;
b) start a new track log file every time the program is started upon user 
confirmation;
c) start a new track log file every new day, like in OziExplorer (probably 
least useful);
d) start a new track log file upon explicit user request.
First three policies might be selected by program settings.

What version of the product are you using?
1.3

Please provide any additional information below.

Original issue reported on code.google.com by s.n.usha...@gmail.com on 5 Feb 2012 at 5:57

berlog / androzic

Allow eventual starting a new track log file #214