Version 8 SR26
(8.26.25337.13001, 2025-12-03)
I’ve just had a bit of drama over V8 opening one day with the screen completely changed, to a maxed-out 4 view, with grid, no command line, and the tool bars all a different size. Also all the aliases lost, and the F key settings gone also.
Anyway, in the process of putting it back to my liking it suddenly crashed, with no crashdump, while editing the options / keyboard.
I have no idea what caused either of these things, but why I am posting about it is I’ve recently being using a dedicated lighting program made in Sweden.
They definitely think differently, and its been amusing and also frustrating getting my head around their logic.
Anyway, one thing they have, and which I suggest rhino adopt, is how they handle a crash.
The program simply automatically saves every command state, since the last save, as, or just after its executed.
If there is a unexpected shutdown, then when you re-open the file it will be in the state of the last manual save, but you are asked if you want to restore the file to last number of unsaved steps. Assuming you want to do that, the file just opens pretty much as you left it, regardless of when you last actually saved it.
For example; I start a new file, and add a few things, and work with it, then, without saving it at all i just shut windows down, ignoring the message about unsaved work.
Then when windows has restarted, i open the program, and choose open new file. It asks me “Do you want to restore the x number of unsaved steps”
And the whole thing I had been doing is restored as if I never left.
This appears to be foolproof so far; there are no options to adjust or disable this; its just a built -in thing. Easy. No Drama.