But again, that requires me to trigger it. A timer would not. It should happen automatically. Many major editing programs like Word/Photoshop/etc do that.If this option is checked then the project is saved before compilation starts. It doesn't matter whether compilation succeeded or not.
I don't know. But a timer-based backup save would solve whatever problem it was.What happened that caused the IDE to crash and the data to be lost?
No. I was porting a large chunk of VB6 code so it wasn't compilable. And I don't assume the program will crash.Didn't you save the project at all for several days?
But again, that requires me to trigger it. A timer would not. It should happen automatically. Many major editing programs like Word/Photoshop/etc do that.
I don't know. But a timer-based backup save would solve whatever problem it was.
No. I was porting a large chunk of VB6 code so it wasn't compilable. And I don't assume the program will crash.
And yet Microsoft/Adobe/etc have failsafes.Let's face it is not a huge task.......
That's why I said "save to a backup folder". It won't copy it from the backup to the real one till you actually save.had the program automated we would have some other user complaining that autosave overwrote changes he didn't want to do.
This is not what we understand from your thread title: "This is the third time B4A has crashed and lost a full days worth of code"I dont know why it crashed. It might have been the computer itself