Quote:
Originally Posted by kaufman
Quote:
Originally Posted by kaufman
I think this option is important, because right now pressing on any group except Tags shows the same list of books. Wouldn't it make more sense to have the subset related to that grouping show?
|
Quote:
Originally Posted by chaley
I don't understand what you are saying.
|
If you don't select a grouping and close the grouping drawer, it shows you a list that contains all of the book in your library.
If you select the tags grouping and then close the grouping drawer without selecting a tag, it shows you a subset of your library that only contains the books that have a tag.
If you select any other grouping and close the grouping drawer, it shows you a list that contains all of the book in your library whether they are a member of that grouping or not.
To me, the behavior for tags makes more sense. If I have shown interest in a grouping, the thing I want to see by default is the books that belong to that grouping. Currently, the default when I select a grouping is to show me all the books in my library, whether they are relevant to that grouping or not. |
Actually, I think this is a bug. The same thing will happen for any is_multiple custom column. It should add an empty entry if the column is empty.
Quote:
Quote:
Originally Posted by chaley
But you are asking that it do something very different from long-pressing on an item. Long-pressing an item does the equivalent of a virtual library. Tapping an item simply shows those items but does not affect tapping on some other item.
|
I think I just didn't say it very well. I think that a long press on a grouping should pop up the same dialog box that currently pops up for a search on a sub-grouping within a grouping. "How do you want to match the books?" "Cancel/Not Matching/Matching". So, if you long pressed on publishers, "Not matching" would create the virtual library of books without publishers, "Matching" would create a virtual library of all books with any non-null value in the publisher field. I think that this is more useful than just popping up an error message. Its also something that people are likely to try.
|
You are right -- long pressing on a group should do a :true/:false search on that group. However, for that to work in the DB the empty value must be there to be found.
So in the end we are still at the original question: do I add an option not to show <<>> books? I am still thinking ...