[rpcameron]

When a recording is selected for deletion, a confirmation prompt is presented to the user with No/Cancel as the default option; additional action on the part of the user to select Yes and then press Enter/Select ought to be enough on the part of the addon.

So you think it makes sense to have the same prompt when deleting 1 recording vs deleting all recordings. Even when probably 99.99% of users would never want to delete ALL of their recordings. Also you realize the GNU devs made a similar change to rm so you can't run "rm -rf /*"

So you want the addon to give you a second confirmation prompt when you are deleting a group/folder? Something like "Are you really, really, really certain you want to delete these files?" That's a bit excessive, redundant and unnecessary. And while your reference to GNU's `rm` providing a prompt for disastrous deletions is valid, other implementations of `rm` do not. GNU adds too many unneeded features and bloat to their utilities, and in general I try to use better alternatives when I can.

Furthermore, if a deletion did accidentally happen you can change the view options in the addon to display deleted recordings and then restore them. If this happens frequently enough, a user can change how long the backend waits before purging deleted recordings from disk in the backend's settings.

First, if you don't have the backend setup right, the recordings will be wiped the first time you make this mistake and any changes to the backend after that are pretty pointless. So you're still putting all the expectations on the user. Some of my recordings are pretty old and could not be replaced if I lost them. It seems like you don't think this is the case unfortunately.

So you are conceding that the problem is with your backend configuration then? If you haven't properly set up your backend, then there really isn't any need to complain. The problem is not the addon, but it is with your configuration; you cannot expect the addon to query the backend when a user does a delete, and notify the user that their backend is not set to retain deleted recordings. At some point you have to accept responsibility that the problem is user error, and not the software.

Personally I find it onerous that changes a user has made in their own personal setup in the way the application/addon responds to remote commands is a problem/bug in the addon rather than in the modified workflow. If a user made modifications to the default workflow, and that is the source of the frequent deletions, then perhaps the problems are with the modifications made, and not the addon.

I'm not sure I know what you're describing here. What are the "changes a users has made", "modified workflow", "default workflow", and "modifcations made". As far as I know am deleting files the normal way.

Part of the problem is also the setup on my remote. I have a DVR button, and depending on certain events it will go to either the current recording or the DEFAULT recording group. About 95% of the time it goes back to the current recording. The 5% of the time it returns to the DEFAULT recording group is when I delete everything. So part of the issue is figuring out why my DVR button the remote does this, but I think its a secondary issue. Even if my remote was working the way it should, I still don't want to have the chance of deleting all my recordings.

As you previously posted, you claim your problem stems from the way your remote is configured. It appears from your comments that your problem is that you don't understand your configuration.

Also, in this thread there are two posts of yours that have been edited/removed. One of those posts indicated that this situation often happens when you are tired and not fully awake/aware; removing the post showing the level of user error that is behind this situation is a bit disingenuous, wouldn't you say?