hi,
since I updated from 1.10 to 1.30 beta (->2 ->4) there are no back up files generated any more.
This is poor, because if a file has been changed by a couple of faulty commands during developing and/or some lines have been deleted, and then F5 or F7 have been pressed, the correct old version is overwritten and can't be restored...

where can the backup feature be reinstalled?

1.30 and above has a different scheme for storing backups.

There is a boolean flag in the preferences to indicate when rewriting a file, whether it should be really deleted or whether it should be stored in the trash / recycle bin.

So you can recover your file by pulling it out of the trash. If you've done multiple saves, you will find multiple copies of the file in the trash.

hi,
thx, but what is the recycle bin? The Windows trash basket?
Anyway, it would be great if the back up files had been physically stored in the current directory (e.g. the best way was, if the file name was myfile.c, then the backups would get the extensions myfile~1.c, myfile~2.c, myfile~3.c and so on...)

And it would be even greater if there was a file... submenu with an option "delete old stuff"...

The "best" solution is to allow "undo" even for the saved files. Currently, "undo" information is lost every time file is save and the file is saved every time there's a compile.

Your suggestion is also good. I'd probably delete them when ROBOTC is closed to prevent cluttering up your directory with lots of copies of the file. And I would also probably limit to "N" (N being a small number) the number of versions that are saved.

PS. Regarding your struct bugts. Some are fixed in 1.36/1.37. If I had your email address I'd of sent you a message. You can contact me at dickswan@sbcglobal.net.

that would be fine.
the files maybe could be renamed circle-wise (?) (I want to say, if a new one is generated and exceeds the limt of the maxCount, it gets the maxCount as an extension, and each of the former ones get a decreased number - the oldest (lowest) would be deleted.)

I already have code somewhere that appends a numeric to a filename and auto-increments the numeric. And I have some code that matches the number of files in this format. So rather than a circular buffer, "NNN" would probably simply increment from existing number (if it exists). This way it is easy to tell vintage by simply looking at file name. And "NNN" gets reset to "000" if the temporary files are erased when ROBOTC exits.

ok, perfect !

in 1.38 there are still no backup files at all - are they?

Ford,

You're just going to have to stop making mistakes. It's the only real solution!

Regards,
Xander

Huuh-huuh -
anyone out there?

@dick swan, @tfriez,
could you plz give a statement to these problems?
how is this with the 1.40?
thx in advance!

In 1.40, the files are moved to the Windows Recycling bin every time the program is compiled or saved. We are still working on adding the increment addition to the file name.