Current explanation:
// presets.ini/tmp are ignored after reprogramming unless this is defined
Would this be accurate as another way to describe this? :
// presets.ini/tmp are initially ignored, then overwritten with uploaded programming and changes made with colorchange mode or WebUsb unless this is defined
I think that’s pretty confusing too.
How about:
// Keep save files across programming.
// By default, ProffieOS uses the time of upload as a way to validate that the save files
// are created by the same OS as the currently running OS. If the time stamp in the save
// file doesn’t match, the file is ignored and the compiled-in presets are used instead.
// Note that regardless of this define, ProffieOS can write new save files which will not be
// ignored since the timestamp will match.
So if I understand that, that means defining KEEP SAVEFILES causes the time stamp to be updated on upload?
Nope, clearly that text was not good enough.
Trying again.
// Keep save files across programming.
// ProffieOS uses the time of upload as a way to validate that the save files
// are created by the same OS as the currently running OS. If the time stamp in the save
// file doesn’t match, the file is ignored and the compiled-in presets are used instead.
// Note that regardless of this define, ProffieOS can write new save files which will not be
// ignored since the timestamp will match.
// If this define is present, save files are accepted and read even if the timestamps don’t match.
thanks for clarifying.