Undertrey / FarmWatchBot

FarmWatchBot for Ewbf, Claymore, Dstm, CCminer, Bminer, Ethminer, Cast XMR, Phoenix, T-Rex, Gminer, NB miner
GNU General Public License v3.0
92 stars 28 forks source link

Time and date format inconsistency #9

Closed borzaka closed 6 years ago

borzaka commented 6 years ago

I really like your FarmWatchBot! Thank your for your work!

I just want to let you know, that the date and time format is different everywhere you use it.

Some examples:

I think the best format for the file names should look like this: log_20180720_223357.txt screenshot_20180720_223357.jpg miner_20180720_223357.txt

Undertrey commented 6 years ago

Hello.

1) 0 hours 45 minutes 42 seconds 12 miliseconds (this all is current time) 2) 7 month 19 date 10 hour 31 minutes (same with 0.8 - means 0 hours and 8 min)

It is possible to change it but in generally it is problematic because of differend date/time formats in different countries. For me this format is more understandable and this all .log files is needed for me :)

borzaka commented 6 years ago

OK, I understand your point. But if you would use double digits for example, than the file orders would be in order. :) Check this:

miner_7.20_0.18.log
miner_7.20_0.8.log

In this case, the 0 hours and 18 minutes log file "before" than the 0 hours and 8 minutes.

With double digits it would like this and would be in order:

miner_7.20_00.08.log
miner_7.20_00.18.log

Other thing: In the root, you name the logfile like this: log20180729_185506 than you rename it something like this: miner_7.29_18.55 Many information is lost: year, sec. So how about: log20180729_185506 renaming to miner_20180729_185506? It looks easier, and understandable.

I respect your choice, but it's not logical for me.

Undertrey commented 6 years ago

Root logfile name given by Phoenix miner. not my script. In batch programming language digits 00-09 are not a numbers. Will be syntax error.