One week ago I started to write a class in one night, not saved, just closed the lid of the laptop, I was feeling some discomfort in my left eye, and I was to sleep. In the morning I was sick. My left eye was like it has been punched. I barely couldn’t see with it. So that project was there, open, not saved. Saw a doctor, it was some kind of infection she just prescribed some medicines and a treatment for 10 days. I was working as I could, and now “I’m fully operational again” , but…
Seems like Microsoft has reset that laptop last night. I checked that Xojo was open until yesterday, so I wasn’t very worried about it, that class was in a very early stage, but as it took some effort to put it as it was I was counting that the “Xojo recovery” could help.
So I started Xojo and it said “Blah, blah, not saved, blah, do you want to recover?” and I: YES
What Xojo did? Nothing.
It started as if it was any start from zero.
Is Xojo recovery broken?
I do remember a complaint asking to put an option in the settings to enable/disable the recovery, and I see none. But it clearly started a recovery procedure… as if it was set on, and seemed it quietly aborted it after the “YES, recover”.
Known issue? What is Xojo currently expecting about this procedure? Is it broken, half broken, should be enabled, should be disabled? Should have a setting or not?
If I remember correctly for the recover to work you need to:
save at least once
add some code and run (at this point Xojo auto save the code)
the recover will use the code on the last run if no Save after that is done.
Of course, I may remembering wrong. Also Xojo should fix this ‘false hope’ if it can’t recover anything, is annoying to see a “do you want to recover” dialog and nothing happens.
Hmm, your assumptions make sense for my failing case. Only writing, not saving (not even naming it, is was like “project asdfadfsdfa” before the first save when I intended to put some name on it.
I was expecting the usual “code was modified since last snapshot + the system is idle for a several minutes” and then Xojo would update the recover snapshot.
But… Anyway… It saved something, as it said “There’s something here not saved from the last session, want to recover it?” (something like that). Something is not good.
my guess is that something is saved but as your project was not saved once is a case not considered by Xojo and they should fix it. Care to open an issue?
Pretty sure this is a “Windows issue”. Run into similar many, years ago.
Other apps have the same issue eg Word, if you shut the laptop lid midway through editing a document, the edits aren’t saved and you might even find the file is corrupted and unrecoverable.
Down in the bowels of the Windows BIOS there is a setting somewhere to the effect that it allows “fast saves” to be cached in memory and committed to disk in background. By default this is ON.
Turning it OFF forces file saves to be flushed to disk immediately, but at the expense of having apps hang momentary when saving because (in Windows) it also forces the save to be done synchronously, ie the app hangs till the save finishes.
I leave it to you to take a close look at your BIOS settings and what they imply.
, but…