Skip to content

v1.0.2 - the layer kind could be changed but never saved

Choose a tag to compare

@corderro-artz corderro-artz released this 14 Sep 20:52
· 609 commits to main since this release

Three faults met in the ingredient editor's Dynamic / Static toggle, and every one of them shipped.

Fixed

The toggle was not an edit. Save is gated on "has anything changed", and the kind toggle never said it had — every other control on the colorize rail did. So a session whose only change was the layer's kind left Save greyed out, and the change could not be saved at all. That is the reported symptom: "saving an item as Dynamic doesn't change the Static type it has."

What it would have written was invalid. Changing the kind spliced the new setting into whatever the layer already carried, which is right while the kind stays the same and wrong the moment it changes. Dynamic → Static produced a static layer with two colorization entries, which the validator refuses outright; Static → Dynamic produced a layer rolling fifty-fifty between the new range and the color it was meant to replace. A kind change now rebuilds from what the rail shows.

Nothing on the editor's save path validated. The invalid book above was written without complaint and only failed later, on a screen nowhere near the edit. The editor now validates the layer it is about to write.

Switching to static asks first. It is the one kind change here that loses something you cannot reconstruct from the screen: a static layer carries exactly one fixed color, so every rolled hue/saturation range goes. Asked at the toggle rather than at Save, because the rail hides the range controls the warning is about the moment the kind changes.

Downloads

Archive For
single-file-net10 Start here if you have the .NET 10 runtime — one .exe, 14 MB
single-file One .exe, no runtime needed
framework-dependent A folder, needs the .NET 10 runtime
portable A folder, no runtime needed