No worries, it's likely that I just cooked up this word ("autosave") ! I think it could be helpful if, while I am editing a game in a database, the changes I have been doing are automatically saved (according to some condition, for instance, every x minutes).
Best
Last edit: Gregor Cramer 2017-07-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The main benefit I can see is that if I do something wrong or if something wrong happens in the system/application/scidb then I don't lose the work.
Automatically saved into the database, or as a backup?
I don't which one is better, maybe the clipbase? But it needs to be restored at the next startup, in this case.
Last edit: Gregor Cramer 2017-07-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The main benefit I can see is that if I do something wrong
Scidb has an undo/redo mechanism, and this mechanism works perfectly (no error report yet).
or if something wrong happens in the application/scidb
A bug in Scidb results into an error message (if the operating system is POSIX conform), and even emergency close of the applications is saving the changes in a backup file.
or if something wrong happens in the system
Scidb is even catching a shutdown of the system, the only thing is a system crash, but did your Linux installation crash ever?
Please note that Scidb provides something like a "fast save", use Control-V + Enter.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, it happened to me every now and then (quite recently, but before the novel feature of the tiled layout) that I lost some long variations.
Reasons were of all kinds:- my mistakes (some even very stupid, once I hit ctrl+S instead of ctrl+R - to replace the game- and everything was blocked after I clicked "ok")- system blocked to due the engine: my laptop very often runs at the limit of its (quite large) RAM and it happened to me that starting stockfish in scidb blocked the SO (Ubuntu 16.04 currently)- entering very long and complex variation with many many subvariations causes the application to be very slow till crash (I already know this may be because of the logging information).- others, but I don't remember now, and it's very difficult to report them
I didn't know about ctrl+V+Enter, but in any case it's difficult to remember to hit this often. A lot of text-editors have autosave enabled by default. Scidb is obviously not a text editor, but you can think of it as a .sci editor (or pgn editor) at times.
I have to think about a concept, such an "autosave" feature is quite more complex than it sounds. It's likely that I postpone this until I have implemented another planned feature: versioning of games in .sci databases. This is like a repository, you can examine all the changes, and it will be possible to revert to a previous version. I've already implemented the feature for showing exact differences between version of games. And this might be the right place to add this "autosave" functionality, in this terminology "autosave" is nothing else than writing an "emergency version".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No worries, it's likely that I just cooked up this word ("autosave") ! I think it could be helpful if, while I am editing a game in a database, the changes I have been doing are automatically saved (according to some condition, for instance, every x minutes).
Best
Last edit: Gregor Cramer 2017-07-28
I'm sorry that I don't know what a classic "autosave" is. Please give me a more detailed description.
The main benefit I can see is that if I do something wrong or if something wrong happens in the system/application/scidb then I don't lose the work.
Last edit: Gregor Cramer 2017-07-29
I'm not convinced:
Scidb has an undo/redo mechanism, and this mechanism works perfectly (no error report yet).
A bug in Scidb results into an error message (if the operating system is POSIX conform), and even emergency close of the applications is saving the changes in a backup file.
Scidb is even catching a shutdown of the system, the only thing is a system crash, but did your Linux installation crash ever?
Please note that Scidb provides something like a "fast save", use Control-V + Enter.
Yes, it happened to me every now and then (quite recently, but before the novel feature of the tiled layout) that I lost some long variations.
Reasons were of all kinds:- my mistakes (some even very stupid, once I hit ctrl+S instead of ctrl+R - to replace the game- and everything was blocked after I clicked "ok")- system blocked to due the engine: my laptop very often runs at the limit of its (quite large) RAM and it happened to me that starting stockfish in scidb blocked the SO (Ubuntu 16.04 currently)- entering very long and complex variation with many many subvariations causes the application to be very slow till crash (I already know this may be because of the logging information).- others, but I don't remember now, and it's very difficult to report them
I didn't know about ctrl+V+Enter, but in any case it's difficult to remember to hit this often. A lot of text-editors have autosave enabled by default. Scidb is obviously not a text editor, but you can think of it as a .sci editor (or pgn editor) at times.
Last edit: Gregor Cramer 2017-07-29
I have to think about a concept, such an "autosave" feature is quite more complex than it sounds. It's likely that I postpone this until I have implemented another planned feature: versioning of games in .sci databases. This is like a repository, you can examine all the changes, and it will be possible to revert to a previous version. I've already implemented the feature for showing exact differences between version of games. And this might be the right place to add this "autosave" functionality, in this terminology "autosave" is nothing else than writing an "emergency version".