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?
|
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
view manager
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