Quote:
Originally Posted by davidfor
Another case of wanting the software to read your mind!
How is it supposed to know the difference between opening a finished book to check something or opening it to reread the book? Or the times you reopen a book to check some detail, but end up rereading it.
For this sort of thing, there has to be a decision made in the design of the application on what to do. Kobo made it in a fashion you don't like. From a usability point of view, I believe this way works better. Reopening the book is treated as starting to read it. If that isn't what is happening, you mark it as finished when you close the book. Otherwise, you would need some other mechanism to indicate the reread.
|
Hmmm...What I would like is for the software to be able have a book marked as "finished" stay marked no matter what. Even if I do decide to re-read the book, I still finished it at some point, so it should still be marked as "finished". Why couldn't it be marked as both "finished" and "reading" simultaneously? Is there only one field in the database for status? If so, wouldn't it be possible to make multiple yes/no fields?
Shari