View Single Post
Old 06-11-2014, 02:43 AM   #17
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,476
Karma: 8025702
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by BetterRed View Post
If I add and remove values in the suggested custom column in the Metadata Editor they can get reordered. If I edit them in the Book List via F2 they don't seem to get reordered (but I am not sure that's 100% true). However, space is at a premium in the book list, so if there are more than a few values its more convenient to edit them in the Metadata Editor.

My experience is that in the Author column the order of 'values' is always preserved - no matter what. So when the custom column did not behave that way, ie values got reordered, I tried to make it happen with the Author names, in case I was mistaken. I couldn't, but I wouldn't want or expect that I could.

In other respects a Names custom column behaves like the Authors column, including the Use author sort in Tag Browser and Author sort name algorithm tweaks.

As far as I can tell its only in the preservation of the order of values when they're edited via the Metadata Editor dialogue that a Names custom column doesn't behave like the Author column. I don't mind that they get reordered, but if they weren't then I could live with that too.

BR
You are correct. The edit-metadata (single) editor widget unconditionally sorts the field even if is_names is set. This is wrong, and I have submitted a fix.
chaley is offline   Reply With Quote