Open GoogleCodeExporter opened 9 years ago
Please note that in current version (0.2.2), the "deleting watch" function is
not
directly accessible and doesn't have confirmation dialog
I guess you're talking about development branch
Original comment by thibaut....@gmail.com
on 21 Apr 2008 at 10:55
So if i understand correctly, you want to remove the confirmation and instead
implement undo/redo?
Why this would be better than the confirmation? I dont really see the use if we
have
a confirmation because i think the user is sure to remove it if i answers to
remove
the watch in the confirmation
Original comment by woutclym...@gmail.com
on 22 Apr 2008 at 5:42
Never Use a Warning When you Mean Undo (Aza Raskin)
http://www.alistapart.com/articles/neveruseawarning
Original comment by thibaut....@gmail.com
on 22 Apr 2008 at 9:45
from GNOME HIG :
If an action is very dangerous, and there is no way to undo the result, warn
the user and ask for confirmation. Only do this in extreme cases, though; if
frequently faced with such confirmation messages, users begin to ignore them,
making them worse than useless.
In all cases, the user's work is sacrosanct. Nothing your application does
should lose or destroy user's work without explicit user action.
http://developer.gnome.org/projects/gup/hig/2.0/principles-forgiveness.html
Original comment by thibaut....@gmail.com
on 22 Apr 2008 at 9:50
The problem is that, as I thought, implementing this is quite hard for the
minimal
return-over-investment (after all, specto doesn't manipulate "complex
documents", it
doesn't require multi-step operations, etc.)
http://dotsony.blogspot.com/2009/04/okay-take-deep-breath.html
Original comment by nekoh...@gmail.com
on 25 Apr 2009 at 12:13
so bad :-(
yesterday i was thinking again about that issue while deleting a watch
i would have liked not be disturbed by a popup window asking me if i'm sure
while
trying to delete it whereas an undo menu entry would have avoid all these popup
windows
Original comment by thibaut....@gmail.com
on 25 Apr 2009 at 5:52
Original issue reported on code.google.com by
nekoh...@gmail.com
on 21 Apr 2008 at 10:41