I'm fairly new to Scratch, I'm using Scratch 1.3 release of 2-Sep-08.
I was working on a fairly large project, I saved and exited. When I came back all my recent changes were lost.
I noticed a file tmp0 sitting next to my SB file.
I renamed it as test.sb and opened it and lo-and-behold it contained my updated project.
It appears that if you choose Save then click exit before the 'screen flicker' then your changes may well be lost.
Scratch should really wait until the save is finished before exiting.
Thx, and apologies if this is a duplicate bug report.
Offline
Dan01 wrote:
I press save like twice, just to make sure ^.^ I think they should add (on windows as I believe it's already on mac's) a "do you want to save your changes" pop-up when you press exit, just to stop this.
Yeah, on Macs, you use the bar at the top under "Scratch" and select "Quit Scratch." It will then ask you whether you want to save.
Offline
I realize there are work-arounds to the problem, but I'm about to start teaching a group of kids Scratch and it will be hard to make sure they all do it, it will clearly be demoralizing for them to lose a lot of work.
Offline
Hi teachkidstoprogram,
as Dan01 has correctly pointed out, this problem can currently only happen in the Windows version, if you quit Scratch before the saving process has completed. We're planning to implement a different quitting mechanism for the next release, which will only pop up a dialog if the project has unsaved modifications, and which will wait until saving is complete before quitting back to Windows. Hang on!
Offline
Great news, thanks!
At the moment, on Windows at least, Scratch is 'unusual' in that when you exit it's not clear if you have unsaved changes so it will be great if that's clarified in the new version of the dialog.
Offline