|
Group: Forum Members
Posts: 13K,
Visits: 78K
|
Even having read that other thread, I still don't see the point of this. The Backup Definition Files tab lists the existing XML files. It even lists their location on disk under the Path column. I understand that you accidentally deleted your XML files, but a user could also accidentally delete a file they had exported, if they even bothered to export anything in the first place. Additionally, the default location for these files is a Reflect folder under the user's Documents folder. There is a reasonably high chance that someone using Reflect will be backing up or cloning their Windows partition, or at least their Documents folder (via File & Folder backup), in which case they would be already have other copies of those XML files in their backups or clones, which could be used to help recover from accidental deletion. But more to the point, if the file is ALREADY in XML format, then what is the point of offering an "Export to XML" function? If you want to store a backup copy somewhere, then just go to the location shown under the Path column (you can even get there quickly by right-clicking the definition file and clicking "Open Containing Folder"), then just make a copy of the XML file(s) you want to back up, and store the copy somewhere. You could optionally even store multiple XML files together in a zip file or something. There's your "export", no application update required.
|