(03-27-2021, 10:35 AM)Dean Roddey Wrote: I've been banging around today and adding more tests in that area and am not seeing any sort of issues with the time formatting, so I dunno what's going on there. I thought maybe something had gone wrong wrt to not providing the fill character, just the width, but that seems to be working fine also.
There were some changes related to faulting in stuff in the time class that correspond to basically 5.4.908. But I don't see any issues there.
And the other weird thing is that it's clearly replacing some of them, else they'd have all of the tokens still in the string. Just going from those examples it's only failing on h and d tokens, but that may just be happenstance.
Hi Dean, I was thinking more on this. The driver stores some history and settings in text files. I believe it's the data taken from those text file fields where the formatting issue is appearing on. Is it possible that whatever method the driver uses to get to that data could have a little bug in it maybe?
As an example the history file looks like this inside:
14010804003710000|1|Water Grass|11
14011668003230000|1|Water Grass|11
14012532003780000|1|Water Grass|8
14013163931030000|1|Water Grass|0
14013396002650000|1|Water Grass|8
14014944777310000|0|Side Grass|3
Also not sure if I should be posting here or is there a 6.x Beta section for discussions? Let me know or move this to there if makes more sense.
Thanks
-Mike G