Hi all,
I'm in the process of loosening MS's grip on my workflow, and have recently purchased NX Universal. I admit, I've been spoiled by Word's autosave function, but I'd rather not use Onedrive anymore. I have searched, and the only info I've found on Textmaker autosaving is outdated, referencing the "Files" tab in Options. There is a "Backup" tab, but the options seem to refer more to snapshots taken at intervals, rather than an actual autosave of the file I'm working on, saved to the folder I opened it from.
So is there an actual Autosave feature? Thanks in advance.
Autosave in Textmaker?
-
raitis.veksejs
- SoftMaker Team
- Posts: 148
- Joined: Fri Sep 15, 2017 1:29 am
Re: Autosave in Textmaker?
TextMaker's System for Data Loss Prevention
TextMaker employs three key features to safeguard against data loss:
If the writing process is interrupted (e.g., sudden power loss, system crash, or application freeze) precisely when the operating system is updating the file, this could lead to file corruption. With save-on-every-change, the writing process occurs more frequently. Cloud storage platforms (like OneDrive) use sophisticated transactional file systems to prevent this.
Future Development
The primary reason Microsoft developed continuous Autosave was for collaborative editing. Since TextMaker currently lacks a cloud or collaboration model, there is little incentive to develop true Autosave. When pursued, this feature will likely be developed concurrently with collaboration tools, which represents a significant development task.
For now, the combination of Snapshots and Backups offers excellent local file protection.
TextMaker employs three key features to safeguard against data loss:
- Snapshots: Saves recovery files at set intervals (e.g., every 5 minutes) for crash recovery.
- Regular Backups: Maintains previous file versions for historical revision purposes, allowing you to revert major or older changes.
- Prompt to Save on Close: Prevents closing a file with unsaved changes.
If the writing process is interrupted (e.g., sudden power loss, system crash, or application freeze) precisely when the operating system is updating the file, this could lead to file corruption. With save-on-every-change, the writing process occurs more frequently. Cloud storage platforms (like OneDrive) use sophisticated transactional file systems to prevent this.
Future Development
The primary reason Microsoft developed continuous Autosave was for collaborative editing. Since TextMaker currently lacks a cloud or collaboration model, there is little incentive to develop true Autosave. When pursued, this feature will likely be developed concurrently with collaboration tools, which represents a significant development task.
For now, the combination of Snapshots and Backups offers excellent local file protection.