Subj : Squish __ftsc_date bug
To   : andrew clarke
From : Oli
Date : Wed Feb 10 2021 11:04:00

andrew wrote (2021-02-10):

 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.

 ac> -    sc_time((union stamp_combo *)&(xmsg.date_written), (char *)msg->datetime);
 ac> +    strcpy((char *)msg->datetime, (char *) xmsg.__ftsc_date);

What happens if xmsg.__ftsc_date is empty? Local messages don't have an __ftsc_date and it could also be missing for other reasons (messages converted from another message base format, copied/moved in a message editor or tossed by a tosser that doesn't copy the __ftsc_date).

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

.