View Single Post
Old 07-23-2014, 01:08 PM   #11
kaufman
Calibre Companion Fanatic
kaufman ought to be getting tired of karma fortunes by now.kaufman ought to be getting tired of karma fortunes by now.kaufman ought to be getting tired of karma fortunes by now.kaufman ought to be getting tired of karma fortunes by now.kaufman ought to be getting tired of karma fortunes by now.kaufman ought to be getting tired of karma fortunes by now.kaufman ought to be getting tired of karma fortunes by now.kaufman ought to be getting tired of karma fortunes by now.kaufman ought to be getting tired of karma fortunes by now.kaufman ought to be getting tired of karma fortunes by now.kaufman ought to be getting tired of karma fortunes by now.
 
kaufman's Avatar
 
Posts: 873
Karma: 1088610
Join Date: Nov 2006
Device: Galaxy Note 4, Kindle Voyage
Quote:
Originally Posted by chaley View Post
I am looking at how to do that. It isn't at all straightforward. I am almost certainly pushing it to the next cycle.
Something to look forward to. Excellent.

Quote:
Originally Posted by chaley View Post
It is there because it must have access to the correct custom column definitions, which 1) are available only in a book and 2) can change from book to book.
I keep forgetting that some people might have their custom columns on a book by book basis. I have three custom columns, and they exist in every book in my library.

I think your solution to just show a message telling people where to find it is a good compromise. The other thing you could do would be to have a function to do a custom column finding scan. Then you would have the entire list of them and could just have one "select details view" at the library level. Probably not worth the effort.

Last edited by kaufman; 07-23-2014 at 01:18 PM.
kaufman is offline   Reply With Quote