Subj : Squish __ftsc_date bug / JAM bug
To   : andrew clarke
From : Oli
Date : Sun Feb 14 2021 11:28:30

andrew wrote (2021-02-10):

 ac> 10 Feb 21 09:56, you wrote to Kai Richter:

 O>>>> It's just a simple bug ...

 ac> I suspect the patch below fixes this, but I've not tested it.

 ac> It's also necessary to verify it doesn't break when rescanning *.MSG and
 ac> JAM bases.

I tested it with a JAM base and it still works. But it turned out a rescan from a JAM base also modifies time stamps:

Original:
Date and time      : 09 Feb 21  06:31:33
Date and time      : 09 Feb 21  05:08:19
Date and time      : 07 Feb 21  18:49:35
Date and time      : 10 Feb 21  03:55:02
Date and time      : 10 Feb 21  08:48:36
Date and time      : 10 Feb 21  12:23:00
Date and time      : 10 Feb 21  13:11:33

After rescan from JAM:
Date and time      : 09 Feb 21  06:31:32
Date and time      : 09 Feb 21  05:08:18
Date and time      : 07 Feb 21  18:49:34
Date and time      : 10 Feb 21  03:55:02
Date and time      : 10 Feb 21  08:48:36
Date and time      : 10 Feb 21  12:23:00
Date and time      : 10 Feb 21  13:11:32

Which means Squish can be fixed, but JAM has the same problem (I tested JAM with hpt from github master without any patch).

Maybe a problem/bug within SMAPI (JAM jammed into the Squish API)?

---
 * Origin: . (2:280/464.47)

.