Quote:
Originally Posted by curt.clifton
Can you say a bit more about how this trash would work?
|
I'll leave how it would work to the UI experts. What I know is that currently it is frighteningly easy to unintentionally trash invisible items in the same action as intentionally trashing visible ones.
OmniFocus is a bit of an odd case in that its function requires that much of its content is hidden purposefully; almost every aspect of its proper function involves hiding data out of sight (and out of mind). Also, the hidden and visible content is intermingled in a complex manner. Therefore some sort of special protection seems to be required to prevent hidden items being removed when the user's action was expressly directed at deleting a visible item.
The undo function is too linear, requiring that the user realise at once that their action had unintended consequences, which may be true in many cases but not all.
I understand your earlier caveat about confirmation dialogs, but I don't think the use of a sound effect or animation quite hacks it either. It could be said that there are two different things going on with delete: firstly, the normal word-processor-type deletions made as part of the editing process, for which the undo feature has a good pedigree as being perfectly adequate; and secondly, the deletion of file-like and folder-like items for which the staged deletion of the Finder could be a closer analogy. The big difference with the Finder is that the content of a folder is always visible when the folder is open; in OmniFocus the content may or may not be visible, depending on view settings.
As a stop-gap I'd accept an alert on deleting a folder, to ask something like "This folder contains items which are hidden due to current view settings. Do you really want to delete this folder? [[cancel]] [delete]", but it's not ideal. Perhaps it should only be possible to delete a folder when the view is set to show "All Projects", with an alert appearing when attempting to delete in other circumstances.