I've heard of a lot of Scratchers that have lost their hard work because they didn't save it every few minutes, I think that Scratch should make it automatically save projects as your working to prevent awesome projects from being lost.
Offline
I support. It's annoying when Scratch becomes unresponsive because of long scripts (or just because it feels like annoying me).
Offline
Sorry, but I don't support. What if you were testing possible modifications to a complicated script, it auto-saved, the test didn't work, and you forget how to undo it? (remember, most of us don't make back-ups)
After about 3 seconds you'll find a way to counter my example, I'm sure.
Offline
Molybdenum wrote:
Sorry, but I don't support. What if you were testing possible modifications to a complicated script, it auto-saved, the test didn't work, and you forget how to undo it? (remember, most of us don't make back-ups)
After about 3 seconds you'll find a way to counter my example, I'm sure.
It could be like on MS Word where it only opens the autosaved version if it detects that it crashed.
Offline
Molybdenum wrote:
Sorry, but I don't support. What if you were testing possible modifications to a complicated script, it auto-saved, the test didn't work, and you forget how to undo it? (remember, most of us don't make back-ups)
After about 3 seconds you'll find a way to counter my example, I'm sure.
Offline
I support, if there's a way to turn it off.
Offline
thebriculator wrote:
I support, and +1 to the above.
+2
Offline
Mokat wrote:
Molybdenum wrote:
Sorry, but I don't support. What if you were testing possible modifications to a complicated script, it auto-saved, the test didn't work, and you forget how to undo it? (remember, most of us don't make back-ups)
After about 3 seconds you'll find a way to counter my example, I'm sure.
RedRocker227 wrote:
Molybdenum wrote:
Sorry, but I don't support. What if you were testing possible modifications to a complicated script, it auto-saved, the test didn't work, and you forget how to undo it? (remember, most of us don't make back-ups)
After about 3 seconds you'll find a way to counter my example, I'm sure.It could be like on MS Word where it only opens the autosaved version if it detects that it crashed.
Offline
bobbybee wrote:
thebriculator wrote:
I support, and +1 to the above.
+2
yay!
Offline
RedRocker227 wrote:
Molybdenum wrote:
Sorry, but I don't support. What if you were testing possible modifications to a complicated script, it auto-saved, the test didn't work, and you forget how to undo it? (remember, most of us don't make back-ups)
After about 3 seconds you'll find a way to counter my example, I'm sure.It could be like on MS Word where it only opens the autosaved version if it detects that it crashed.
I'm not sure you can detect a crash; its definition is pertty vague. Ex. Some people only consider a crash to be a crash when scratch closes itself with a very bad error, while some consider even minor things like extreme lag a crash.
Offline
I support. You should be able to turn on, and off autosave.
Offline
Molybdenum wrote:
RedRocker227 wrote:
Molybdenum wrote:
Sorry, but I don't support. What if you were testing possible modifications to a complicated script, it auto-saved, the test didn't work, and you forget how to undo it? (remember, most of us don't make back-ups)
After about 3 seconds you'll find a way to counter my example, I'm sure.It could be like on MS Word where it only opens the autosaved version if it detects that it crashed.
I'm not sure you can detect a crash; its definition is pertty vague. Ex. Some people only consider a crash to be a crash when scratch closes itself with a very bad error, while some consider even minor things like extreme lag a crash.
Well maybe just if it closed without saving. Then it could could come up with "This project was closed without saving. Would you like to open a recovered version of this project?"
Offline
RedRocker227 wrote:
Molybdenum wrote:
RedRocker227 wrote:
It could be like on MS Word where it only opens the autosaved version if it detects that it crashed.I'm not sure you can detect a crash; its definition is pertty vague. Ex. Some people only consider a crash to be a crash when scratch closes itself with a very bad error, while some consider even minor things like extreme lag a crash.
Well maybe just if it closed without saving. Then it could could come up with "This project was closed without saving. Would you like to open a recovered version of this project?"
That's a good suggestion.
Offline
trinary wrote:
RedRocker227 wrote:
Molybdenum wrote:
I'm not sure you can detect a crash; its definition is pertty vague. Ex. Some people only consider a crash to be a crash when scratch closes itself with a very bad error, while some consider even minor things like extreme lag a crash.Well maybe just if it closed without saving. Then it could could come up with "This project was closed without saving. Would you like to open a recovered version of this project?"
That's a good suggestion.
+1.
Offline
I support, but only if there is an option to turn it off.
Because I like to experiment with Scratch a lot, and I sometimes use Scratch to make my signatures and such and then I either clean it up or enhance it a bit in GIMP.
Offline
so in the end it all comes down to this:
Have an option for auto save
or
Have a button that pops up saying "This project was closed without saving. Would you like to open a recovered version of this project?"
As long as Scratchers don't lose there projects I think that these are both great ideas
Offline