No, it does not have this functionality.
You would need to submit a feature request to IDM by email.
As a workaround for now, I would suggest using a TrueCrypt volume or perhaps use Window's built in folder encryption, and point UEStudio to that folder to save all the backups. There is really no reason to keep a backup file in the same path as the original file. It just clutters the path.
I use a version backup on save (Advanced->Configuration->File Handling->Backup: Version Backup). Format: $b$p$n($c)$e
That format of the version backup will save F:\Documents\test.txt
where X:\uebackuppath\ is the Default Backup Directory for UE, and # is the incremental save number for multiple versioned backups. You may prefer to save other information there, but this works pretty well for me.
I use a bit of an odd method to open UEStudio, personally, which allows me to handle such issues.
I have written a small utility that is launched in place of UEStudio, anytime UEStudio is called to be opened by the system. What it does is the following:
- Check to see if an instance of this utility is already running in background. If so, pass filenames to UEStudio and exit. If not, continue...
- Check to see if a certain TrueCrypt volume is mounted. If not mounted, it asks for the password, then mounts the volume.
- Set Environment Variables TEMP and TMP to point to a temp path on the TrueCrypt volume. Since this utility will be launching UEStudio, then these values will only be used by UEStudio, and will be removed once this program exists. That means this launcher program has to remain resident in memory, hiding until UEStudio is closed.
- Check to see if UEStudio is already running. Any command-line flags are interpreted, and depending on whether configuration is for "open in new instance" or "existing instance", it will either pass a file to the already open UES or open a new instance of UES with that file.
When UES is closed, then the utility closes, which removes the changes to the Environment variables. While it is possible to dismount the TrueCrypt Volume at this time, I don't do this, since I may need it again later and it makes it more troublesome having to enter password longer than 32 characters for my TrueCrypt volume every time I want to use UES.
As the TrueCrypt and volume is not automatically dismounted when I exit UES, if I want things to remain secure, I must manually dismount. Not difficult to do, but I generally keep it open for as long as I am working at my desk. If I step away for lunch or whatever, I dismount the TrueCrypt volume after closing UEStudio, if open.
Since it only has to mount the volume the first time it is run (until I manually dismount), then after the first run, starting UES is actually much faster than starting UES normally, if UES is already running, because this much smaller program is loaded and passes command line parameters to the running copy of UES instead of having to launch a new instance of UES, pass parameters to original copy of UES, then close the new instance.
All my backup files are configured to be saved on the TrueCrypt volume, so that they are always encrypted. The file originals that I am working with may or may not be encrypted, depending on the sensitivity of the file, but backups are always encrypted as a safety net.
Temp files, which can also be a security concern, can be routed to the TrueCrypt volume, but this is trickier. You need to change the environment variables TEMP and TMP, but ONLY for UEStudio. This is why UEStudio needs to have a launcher when you do these things.