Quote:
Originally Posted by chaley
One possibility: create a column per icon using one of the types that does not appear in the tag browser, e.g., int. This sort of column has almost zero impact on calibre's performance. You would leave the value empty (or perhaps not) and set the width to be just enough to contain the icon. Everything would line up nicely, and the pattern of icons might convey as much information as the icons themselves.
|
Telepathy again, I just came back to tell you I had done exactly that. I gave the int columns meaningful
Lookup names and one letter
Column headings so no need to change the width. And you're correct in saying that the pattern is as important as the individual icons, in my case some patterns would reveal violation of mutually exclusive conditions.
Quote:
Originally Posted by chaley
As regards the standard column, it would be a fair amount of work to add them to the spreadsheet, and no one has cared enough to do it.
|
Seems a shame, but I can see a way to get what I want. I'll add a Better Red Comments column, move what's in Comments into it, and include it in Book Details - then if I see something wrong (in Book Details) I can edit it in the spreadsheet just like everything else.
Thanks again for your help, once again I stumbled on something else when you answered one of of my questions - that's happened on at least two previous occasions. "Here's looking at you, kid"
BR