Fences is dangerous - or am I doing something wrong? - Resolved

My usual PC just died so I'm currently using an old version of Fences on a slow five-year-old Win10 machine. (When I get a new PC I'll upgrade to version 5 but right now I'm stuck using version 3.1.6.1.) I've just noticed that a diary file that I update every single day is not being handled properly. So, to test out Fences' behavior, I tried a different file. My policy is to keep all my important files on external hard drives - NOT on my PC's C: drive. I've had major disasters in the past with other PCs dying on me and causing the loss of files because I was storing them only on the C: drive (and not doing a DAILY backup of them), and I'm taking steps to keep this from happening again. So, to test Fences out, I took an unimportant text file currently sitting on an external HD and dragged it into a Fence on my desktop. I then double-clicked on the file's icon and edited it, then searched for its location, checking the file's modified date to verify that it was the just-edited version. To my horror, I found that Fences had created a duplicate of the file and placed it on my DESKTOP !!! It was THIS file that I edited - the original file remained unchanged! This is NO GOOD! If this PC dies, I'll lose whatever files were on the C: drive that I hadn't yet backed up. How do I fix this? Should I go to the trouble of creating shortcuts for my important files and drag the shortcuts into Fences? Would that work? Also, maybe you can answer a much less important issue I have with your fine program. I have about a dozen rolled-up fences on my desktop (this keeps my changing "wallpaper" backgrounds very visible). They're in two columns and I'd like to space them out vertically but try as I might, I just can't get their spacing to be even. I would think that it would be a simple matter for Fences to allow exact (pixel-by-pixel) vertical spacing of fences. Version 3 couldn't do this, can version 5?