Quote:
Originally Posted by BetterRed
It doesn't default, it suggests.
|
Odd, when I installed the beta, the Pages builtin column was created. No suggestion about it.
Quote:
Originally Posted by BetterRed
You seem to be conflating two issues -- the Column header value of the built-in 'pages' column, and the ability to create a custom column with a Column header value that duplicates a the Column header value of a built-in column.
Please answer my "Why would anyone…?" question
|
As far as I can tell, you seem to be upset that calibre's new column for displaying page counts uses the same column header as the default for the page count column for the Count Pages plugin.
Given that you could not create a custom column with a header duplicating another column until a change to calibre was made very recently, the old saw about a tempest in a teapot comes to mind.
As to why someone would want to do this? I lack the ability to understand why someone would want to duplicate headers. That this happened was likely due to the lack of knowledge that a column header used by a plugin was being duplicated.
Quote:
Originally Posted by BetterRed
You and others have have correctly stated that its the value in Lookup name that matters not the value in Column header… in which case why not let the user change them… given they will have the ability to duplicate them.
|
My reason for not wanting to have builtin column header to be changeable is simply that some utilities I use use the column header and not the lookup name. That I could, in theory, open a library database and rename all the custom columns in custom_columns to 'Custom' is not very useful.