One step backwards, two forwards?

I have a bit of a dilemma. I want to start pushing the advertising of NeverOverwrite again but I'm not happy with one of its current limitations. In the early days (around beta time) a user suggested adding support for subfolders when choosing to begin monitoring a folder. I added this in a rather loose way, but I've never been entirely happy with it.

The reason being, there are several scenarios in which the previous versions of files can appear to vanish. Examples are; moving a file to another subfolder, renaming a subfolder, or moving a subfolder to another subfolder. These are instances where the software currently loses track of the history of the files, and it's too easy to do in my opinion. I have done it myself, and while it's pretty easy to correct (by undoing the move or rename) it's far from perfect.

I've spent some time analysing all the scenarios I can think of and I've come up with 9 that aren't presently handled. Of these 7 can be handled fairly easily but 2 are not straightforward.

For example, moving a monitored file to another subfolder is a scenario in which the user would (quite rightly) expect the history of the file to follow the file itself. But moving a file results in a series of Windows events (not just one) which are not easy to differentiate from the user deleting a file, and creating a new one in another folder which happens to have the same name.

There are some strategies I can use in all these scenarios, but they will take time to implement and test, and I don't believe it's the best use of my time at this stage. I would rather get a solid product released, with a more polished and reliable feel before moving on to this work.

So I've taken the decision to roll back the subfolder support until a later date when 1) I know it can be done, and 2) there's enough users of the current version to justify the work.

Hopefully this is a step back that will get me two steps forward in the long run.