Quote:
Originally Posted by DNSB
Odd. A custom column with it's lookup/search name starting with # (i.e. Pages/#pages) does not seem to cause any issues with the Pages/pages used by calibre.
Can you point to an example of where you are seeing an issue?
|
The main issue was that user cannot create column with a header alreday used. Something I understand, which is why I suggested removing this limitation, a suggestion that was accepted in the master (but still not in the Beta binary)
Quote:
Originally Posted by JimmXinu
A warning for Calibre Sync users: Calibre Sync is incompatible with Calibre 9's library changes.
|
Their is absolutly zero incompatible Calibre 8 and 9s library. The new column is added, even on library that have a column with a hedear "Pages" and no data is lost or overwrite.
Quote:
Originally Posted by BetterRed
I see an issue when the user is presented with list of Column header values which are not unique, from which they must make selection. Here's a couple:
gridview field under cover
Attachment 220258
view manager
Attachment 220259
I have no idea which "Pages" is which.
And, when version 9 is released if I was daft enough to add a custom column with a Column header value of "Publisher" I wouldn't know which "Publisher" was which either.
BR |
Inded, that why I make a other a
PR on calibre to use a extended format "Heading (name)" here too.
If there are other places like this in
Calibre, thanks to report them so that will can changed too. But there will undoubtedly be somes places where an extended format will not be accepted.
Else, for View Manager, that a issue to report to kiwidude, because it is plugin.
I agre that is the kind of confusion that can happen when using a already used heading, and only show them for for column selection,
BUT, saddly, it's not issues
serious enough to warrant renaming the Calibre Pages in something else.
It annoying and confusion, but that all. This may require some effort from the user part, but not that much. Like @DNSB suggest, rename the confusing column, even temporay, if you want manipulate confusing colmun based on their header.
Calibre developement cannot be retstricted of the use of a header on the principe that a user could already use it. Even in the case of a "often common" custom column name like "Pages".