Recovery

[xahu34]

It might be useful to have a recovery function in PTE, which means that the program should automatically store the actual state of the running project, any 5 or 10 minutes, in a separate directory. So, whenever your system or even PTE crashes, you can reopen PTE and go back to a rather new version, and only the work of a few minutes is lost.

Kind regards

Xaver H.

Munich

[Henri.R]

Good idea, a recovery function, but beware: in some apps, after auto save, you also destroy the history so it's impossible to undo the steps before the auto save.....

Henri.

[JudyKay]

Situations differ, so I think a configurable autosave would be a good idea.

Presently I just develop the habit of hitting Ctr+S every little bit. Still there are a few times when something crashed and I just had to cry a little while.

jk

[xahu34]

Hello Henri,

my idea would be that PTE should save a pte-file any x minutes (x maybe fixed or chosen by the user), without destruction of the history, of course. After a system crash the history would be gone, but at least a recent version of the show under development were still available (be be opened via the file menu).

Best regards

Xaver

Munich

[Henri.R]

Indeed, Xaver, that's the way. (Hoffen wir nur dass Igor es erledigt in 5.2...)

Regards

Henri.

[jfa]

I too would like to see this one implemented.

The user to select the folder where auto-save is made and the time period between saves, and as stated above history is maintained.

[Igor]

Thanks, Xaver!

I plan implement similar feature to the next version 7.5.

Did you see "History of changes" (under File sub-menu) in Google Documents? You can return back state of your project to a day ago or a month ago.

This feature will store only .pte project file (no pictures or audio files).

There will be a special storage (a folder) in system folder (like Templates folder). And the program will pack a project into ZIP archive.

It's a fully automated system, it will correctly recognize when you copy, rename or Save As project inside PicturesToExe or outside in Windows and provide history of changes for cloned/copied/new projects.

Probably I'll add Import/Export to move history of changes to another PC.

There is only minor concern - isn't this system too complicated?

[xahu34]

... There is only minor concern - isn't this system too complicated?

Igor,

Here are some remarks/questions on your proposal:

• Some users may not like to have an automatically growing repository in the background, perhaps not under their control!?
  
• There will be 2 repositories in the system, the automatically generated one in the background, and the one organized by the user himself (his own PTE-files). The user (hopefully) will make back-ups of his own data, but what will happen to the background system? Some users will rely on the availability of this system, and what will happen if the hard disk crashes?
  
• Users who develop their projects on 2 machines (PC at home, notebook on traveling) will have to do a lot of export and import business in order to keep the background systems consistent.
  
• What will happen to projects which will be renamed, moved, edited or deleted outside of PTE?
  
• The recovery system I have asked for, is far from being a kind of configuration management system as you propose, but it would help a user not to loose hours of work in case of a program/system crash and in case that he forgot to make appropriate savings (while avoiding the disadvantages of the present auto-save). Question: Will your method provide this feature at all?
  

I myself got the impression that the planned system may be too complicated for an average user.

Best regards,

Xaver