ALCPU Forums

I have re-edited this request:
Hard coding mm/dd/yyyy is great for USA but the rest of the world uses other formats as default. It is exceeding difficult to do an excel graph. I tried this with excel 2003 using the "text to column" conversion but it gets your date format wrong and I get a converted result assuming text is dd/mm/yy. That screws up graphing day is swapped with month. It did this in my case and probably depends on OS regional setting.

To future proof updates I suggest changing heading in log file header "Time" to literal "Time (hh:mm:ss mm/dd/yy)" so I can write an excel macro that will reformat the data for now. That change will allow me to detect the format changes in some future release. Data for last month like 12/01/12 is ambiguous depending on what your used to.

In my opinion log files should be yyyy-mm-dd hh:mm:ss (which is not necessarily what your OS regional settings are). I think excel will detect that correctly. What do others think is there a general agreement on this?

(Also noticed an extra comma on end of every CPU temperature data line which is not really needed)

BanditQuest wrote:Could you please get the logging to use the date format set by the OS in regional settings. Hard coding mm/dd/yyyy is great for you but the rest of the world uses other formats as default. It is exceeding difficult to do an excel graph because it does auto conversion (open csv file) to internal serial is using dd/mm/yyyy (for me it did this) and that screws up the graphing.

Yes, please do this!

EDIT: Ooops, sorry. If Core Temp log files adhere to System Regional Settings, that is good enough for me.

Naki wrote:Yes, please do this!

I re-worded the request after a lot of testing in excel 2003 I found I can work around problem.

As I see it there are 2 options:

1. Keep using what we have right now. It does conform to your regional setting as in DD\MM\YY or MM\DD\YY.
2. Have a custom hard coded time format, similar to what we see in the log file title.

I can't find anything which will return the correct string with the format you have set in the Regional Settings configuration window.

The Coolest wrote: ↑Fri Jan 04, 2013 12:30 pm ... It does conform to your regional setting as in DD\MM\YY or MM\DD\YY.

Even with version 1.0RC4 32 bit on win 10 (x64) it has always ignored regional settings.
Tested on a few machines all set for "English (Australia)" short date "dd/mm/yy" but log data is "mm/dd/yy", so puzzled by your comment.

Try latest version. What you listed is VERY old.