Quote:
Originally Posted by Asheron
Sadly the keep_in_order doesn't work. It keeps sorting them alphabetically.
|
keep_in_order is working for me.
Be aware, if your custom column type is "Comma separated text, like tags",
Calibre will be ordering it for you.
Use column type "Text, column shown in tag browser" to preserve order.
Use the
add_to_titlepage_entries setting, then look at the title page--that will tell you if keep_in_order is working.
Quote:
Originally Posted by Asheron
Also if there's only one type of ship (only romships) in a fic then the other one (platships) gets the same info that the other one. Is there a way to put the word None when that fic doesn't have a type of ship?
|
I'm not seeing that.
What I do see, is that if
platships or
romships reduces to nothing, FFF doesn't clear the custom column if it already has a value. I would speculate you have left over values from previous testing? Clear the columns, then try again.
FYI, that's a side effect of how FFF treats empty metadata entry strings in general and, as I recall, was declared a-feature-not-a-bug years ago because then it's easy to manually enter a value for such columns and not have it wiped on update.
If you
really want to, you can change
add_to_custom_columns_settings to set your columns to "None" and only override that when there is a value like so:
Code:
add_to_custom_columns_settings:
"None"=>#romshipscol
"None"=>#platshipscol
romships=>#romshipscol
platships=>#platshipscol
But it's not a great idea, from a database theory point of view. Empty cell already indicates "None".