Capture skipped logging Hours:Minutes:Seconds
Serial and TCP terminal for engineering and debugging
Brought to you by:
crun
Menu
▾
▴
1 Attachments
#74 Capture skipped logging Hours:Minutes:Seconds
Last night I was capturing a data stream with the "YMDHS" option checked. The two samples that happened right at midnight had no Hours Minute Second field, just the date. I fixed the problem by nuking those two samples so I can't give a proper sample of what happened, but here is what remains.
AM->PM works properly, PM->AM just logged the new date.
Did another run last night. New sample lshows just what happened.
Ticket moved from /p/realterm/support-requests/28/
Can't be converted:
Please set RT version so I know what version you are using.
Looking at the code, RT is using the system datetimetostr function, with format taken from your machines local datetime settings.
Interim solutions:
Actually if you are using the data for graphing or anything useful, that is a far better idea anyway, as you can sort and filter easily and properly on datetime numbers, and not on the datestrings.
As I try to fix it is does raise the question of what the format should be?
Since the current behaviour makes some sort of sense i.e. it is using you local system format (and working correctly), the question is if this is actually a bug or problem to you at all?
I see that the selction offerred is YMDHS. This is sensible, as it is international (i.e. not suffering from intdeterminate month/day swap.
"2016 05 29 22:57:35"
"2016/05/29 22:57:35"
"2016 05 29 22:57:35"
2016,05,29,22,57:35,
How are you using the datetiime? What software?
What format is best for you?
Is this actually a problem at all, given it is the underlying system behaviour?
Should I really change it?
Custom format strings have been implemented to completely solve this issue, both in terminal and capture. Please test whe 3.0.0.30 is released