Auto-Save Not Working

[awakenedbyowls]

I have it set in the settings under General - but the only time it saves my work is when I save it

I'm checking the Files regularly and it doesn't appear to be saving to the location it's set to - but when I save manually and go to Files I can see it has saved because the thumbnail changes and the time

What am I doing wrong - or is it a bug?

[Dan C]

Hi awakenedbyowls,

This is an internal save only, used in case of something like an unexpected shutdown, dead battery etc.

to save to your file you will need to manually hit the save button in the file selection screen.

Lee

[awakenedbyowls]

11 minutes ago, LeeThorpe said:

Hi awakenedbyowls,

This is an internal save only, used in case of something like an unexpected shutdown, dead battery etc.

to save to your file you will need to manually hit the save button in the file selection screen.

Lee

Would it not be better to just save the file where it's located? That's why I have auto-save set up - so the file in that location is no more than 30s behind in my work schedule at anytime. Just seems like a strange way to do it. I find the whole system of saving highly confusing with iOS - whereas with Windows it's more straight forward and intuitive. Why can't we have at least an option to use it this way?

[DM1]

12 hours ago, awakenedbyowls said:

Would it not be better to just save the file where it's located? That's why I have auto-save set up - so the file in that location is no more than 30s behind in my work schedule at anytime.

Yes it would. The current approach is confusing. Autosave updates the sandbox version only, not the external document. Better than nothing I suppose but many have been caught out. Autosaving should be updating both sandbox and external file (which is what using Save in the Doc menu does).

[Dan C]

Aside from being a limitation of the operating system, I don't think it would make sense anyway.

If you enable autosave over the original file, it makes it much easier to ruin your document with no way back, meaning you really have to start saving history with the file which would inflate it massively. At least this way you always have a recovery method.

Lee

[awakenedbyowls]

17 minutes ago, LeeThorpe said:

Aside from being a limitation of the operating system, I don't think it would make sense anyway.

If you enable autosave over the original file, it makes it much easier to ruin your document with no way back, meaning you really have to start saving history with the file which would inflate it massively. At least this way you always have a recovery method.

Lee

I work by creating a series of numbered files like <filename>_1, 2, 3 etc so I can always go back + I have an archive of progress that gets burned to DVD and deleted eventually from my hard drive. I know there is an option to save history on the software but I just prefer to work this way - this also helps with working back and forward between iOS and Windows.

Not a developer, but I find it hard to believe iOS is preventing you from setting up the app to autosave to a file location? It might cause the app to temporarily lag - but you'd know that and I wouldn't mind if I could see it was saving my work.

[awakenedbyowls]

3 hours ago, LeeThorpe said:

If you enable autosave over the original file, it makes it much easier to ruin your document with no way back, meaning you really have to start saving history with the file which would inflate it massively.

Do you mean setting the app to autosave to file location risks corrupting the file?

Or do you mean by setting it this way you then have to accept that any previous stages in your design process will be lost (unless history is turned on)?

As I say I'm fine with that because I tend to duplicate layers that I'm currently working on so I can work back that way if need be, and then later delete them when I'm happy with the changes.