Fulcrum v4.6.0

Release notes

A hardening release: damaged or malformed files are refused cleanly instead of being half loaded, cancelling the guide now frees your processor as well as the progress bar and the promise about network use is now checked automatically.

Saved sessions you can trust

If the saved move record could not be read or no longer replayed, Fulcrum used to restore the organisation without it; the next save then wrote the file without the record, so the moves were lost unseen. Now the file as it was is kept aside first. The organisation still restores and a message on launch says that only the move record was lost and where the original file was kept. Nothing is deleted.

A saved file whose contents are the wrong shape (a list where a value belongs, a word where a number belongs) is now treated like any other unreadable file: kept aside with a message, never a failed launch.

Opening a plan

A plan file that will not read or whose moves will not replay is now refused with one message naming the problem; where a move is the cause, the message names the first move that fails. Your current session stays exactly as it was.

Numbers the model cannot score

An organisation carrying impossible values (a number that is not a number, an infinite or absurdly large count, a yes or no setting written as text) is now refused with a clear error. Before, such a team could pass every check and score a perfect 100. A team and a unit may no longer share an id.

Cancelling the guide

Cancelling a guide build on a large organisation now ends the worker processes it started, so your processor cores are free again straight away rather than finishing work nobody will read.

Network use, now checked

Fulcrum's only connection of its own is the anonymous daily check for a newer release. That was a promise held by review; it is now checked automatically every time the app is tested, so any other connection fails the build until it is argued for.