Posts: 437
Joined: Nov 2009
Reputation:
0
I think it makes a great add-on and I completely understand the reasoning behind wanting it, especially in cases of limited storage.
My argument is that it should not be available without being an add-on. No offense to Simplicity or any other skin, but there are some things I do not want a skin to do "by mistake." Adding it to core means it might have an API call sitting out there to be called incorrectly. I love the free market approach to skins because it is one of the strongest reasons to use XBMC. But some functionality should not be enabled (even in the API) without the user explicitly installing it.
Posts: 437
Joined: Nov 2009
Reputation:
0
One of the repositories has an add-on for this. I'll check for the name when I get home.
Posts: 26,215
Joined: Oct 2003
Reputation:
187
From what I understand (and please, correct me if I'm wrong) this feature once enabled effectively executes the Delete action on the list once playback is stopped.
So, when a user plays something to the end and does actually want it deleted, they save 1 key press out of 5 (delete, left, select, left, select) -> (left, select, left, select), or potentially more if the delete key isn't mapped and the user must go via the context menu (though I would argue that the fix in that case is to map the direct action.)
When a user plays something and doesn't get to the end, are they still prompted?
What happens if the user just tabs out of fullscreen? Does it immediately prompt, or is it a little smarter?
What happens if the user tabs out during playback, focuses a different item and tabs back to fullscreen to wait for the end of the movie?
When the user plays something to the end and doesn't want it deleted they're still prompted. So you're forcing an extra key press there.
On balance then, is it really making it a better user experience for those that want the feature?
Cheers,
Jonathan
Posts: 1,617
Joined: Jul 2009
Reputation:
11
From what I understand (and please, correct me if I'm wrong) this feature once enabled effectively executes the Delete action on the list once playback is stopped.
So, when a user plays something to the end and does actually want it deleted, they save 1 key press out of 5 (delete, left, select, left, select) -> (left, select, left, select), or potentially more if the delete key isn't mapped and the user must go via the context menu (though I would argue that the fix in that case is to map the direct action.) Yes
When a user plays something and doesn't get to the end, are they still prompted? Only if they press stop.
What happens if the user just tabs out of fullscreen? Does it immediately prompt, or is it a little smarter? Nothing happens.
What happens if the user tabs out during playback, focuses a different item and tabs back to fullscreen to wait for the end of the movie? Nothing happens.
When the user plays something to the end and doesn't want it deleted they're still prompted. So you're forcing an extra key press there. Yes
On balance then, is it really making it a better user experience for those that want the feature? I think that the users that turn it on will be the type that watch more shows that they delete after watching than shows that they dont. Again, this may only hit a small number of users, but I made it sort of for me, and then added it as an option. I'm beginning to think I should take it out and leave it just for me.
Cheers,
Jonathan
To learn more, click
here.