Thread: Is There a Way to Protect Amazon's X-Ray Capability on the Kindle?
View Single Post
Old 01-20-2015, 10:57 AM   #25
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,134
Karma: 60406498
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by DaveLessnau View Post
Sorry for jumping in here, but tilia, in the post above, gives a first step that says:

"You make a custom column of the type "Text, column shown in the tag browser" with the lookup name file...."

Whereas eschwartz says:

"The custom column (of the default type "Text, column shown in the tag browser") is named "#file", titled "Original Filename"."

I'm wondering about what you named the Lookup Name when you created the custom column. Personally, I'm unclear on what should go into that Lookup Name field during the custom column creation process and wonder if the problem might be there on your end as well.
Custom column lookup names can be any single word (no spaces): eg page_count
when you use the lookup name it will be #page_count (the # indicates a custom column name).

The Visible (label) Name does not have to match (and can have spaces).

Page Counts <= Column Label
#pc <= lookup
theducks is offline   Reply With Quote