Quote:
Originally Posted by DoctorOhh
I decided to test the search function and didn't see it on the menu bar so I looked in the drawer and I saw "Search not active" I thought ok I want to activate it where should I go? Shortly I went back and pressed it and was able to test search fine. Possibly I'm the only one that will be confused but I would suggest "Search - not active" or "Search [not active]" or "Search (not active)" or "Search - not active" etc...
Then again maybe it is just me.
|
I forgot about that one.
We have received emailed questions asking how to activate the search function.
What about leaving it empty and letting the magnifying glass be the indication? Or having it contain simply the word "Search"?
Have you noticed that long-pressing on a category item (such as a tag) will search for that item? This behaves a lot like a virtual library, restricting what you see and what grouping operates upon to the results of the search. And they are fast because we can guarantee that we can search directly in the DB.
This is one reason that I introduced the "virtual_libraries()" template function in calibre (new_db only). The idea is to make a composite column (acts like tags) that calls that function (e.g., {:'virtual_libraries()'} ). The function returns the names of the VLs that the book is in. You would then add that column to CC's grouping, which would allow you to select your calibre virtual libraries in CC with a long-press. We (Kovid and I) did a lot of work to try to optimize the performance of that function in calibre, using caches and the like. It is hard to know if we succeeded.