Quote:
Originally Posted by user_none
How would you fix it? Put a dialog box that informs the user what files would be deleted and have them confirm before doing so?
|
Forcing libraries to be in a folder that is created by Calibre might be a way to prevent this from happening again.
Calibre not allowing non-empty folders is a good way too. Still, I'd offer a preset folder name that will be created.
Quote:
Originally Posted by ThR
The sequence should be: read - think about what you have read - understand what you have read - do it.
|
Good theory, but useless in practice.
Too many programs are showering the user with useless messages, after a while you tend to ignore the messages because you
know what to expect from the program.
But, once in a while a program breaks the pattern. Which is when ugly things happen...
Not saying that Calibre did wrong. Just that it obviously wasn't what the user expected.
In this case I'd say it's definitely the users fault, though I too have struggled with Calibre - for some reason I don't like the interface.
(But, it does it's job very well and it's free, so I'm happy to spend a few minutes looking for what I need.)
Quote:
Originally Posted by kovidgoyal
@CRussel: I'm worried that the longer I make the message, the less likely people are to read it.
|
Correct.
A few words that can be gathered at a glance should be enough.
Quote:
Originally Posted by Sweetpea
Or you could do what Microsoft does, ask, ask again, ask again because you might have made a mistake the first and second time, and then ask again, to be completely sure. And maybe even ask again after that!  |
Yees, and help creating a generation that has only learned that these messages are mere reaction tests.
There needs to be a middle ground between "let the user run into a wall" and "ask him at every step if he didn't forget to breathe".