- Textastic for iOS
- General
-
Ideas
+12
Under review
Auto save
Please add an option to disable auto save feature (and add a “Save” button). I work with apps like shellfish in live servers and in the meantime I add some PHP code then I get always errors until I have finished my modifications.
Customer support service by UserEcho
+1 this, I am not a fan of auto-save either for similar reasons, document tab should have * prepended until manually saved if Auto-Save is disabled.
+1 this. I just purchased Textastic for iOS and cannot believe that autosave is the default and cannot be turned off. This is so dangerous when making changes to server based source code. There's nothing in the app description to warn you of this (rather non-standard) behaviour before purchasing, which is a little disappointing.
It is absolutely the standard on iOS and macOS and even required if you are editing files stored in iCloud or in the Files app so that multiple apps can edit the same file using file coordination.
That's not entirely true or helpful. Look at the simplest text editor - TextEdit, there's the usual "Save" and "Save As" no autosaving. Similarly, the legendary BBEdit and even Xcode doesn't save changes until you close the project or manually save. I honestly cannot think of any other decent code editor/IDE which autosaves changes as it's such a dangerous thing to do so I'm afraid I don't understand your reluctance to implement an obvious feature many of us really need. There are plenty of other code editors on iOS which don't autosave (wherever the files are located), but sadly they don't come close in terms of the other functionality of Textastic. Such a shame.
TextEdit and Xcode both use autosaving by default on a fresh installation of macOS, but you can configure it in System Preferences to also ask whether to save your changes or revert to the last explicit save when closing a file.
On iOS, autosave is absolutely the default - there is no explicit save command in Notes or Pages for example.
I do of course understand where you are coming from and why the ability to disable autosave would be useful, I was just responding to the claim that this was "non-standard" behaviour.
Hi agree with you Alexander, but the purpose of most of your customers is different. As you can see from the home page of this site the most common languages used in your App are PHP, CSS, Javascript and HTML...so basically your customer needed something able to work with Web Server. With autosave this is impossible and dangerous. This is the reason I does not use anymore you App and moved to something else.