Quote:
Originally Posted by DNSB
Do you have any indications that Kovid Goyal has used the Count Pages plugins
|
None, but this is a beta version - and therefore subject to material change.
Quote:
Originally Posted by DNSB
and knew that it defaulted to a column header of Pages?
|
It doesn't default, it suggests.
Quote:
Originally Posted by DNSB
Given that option was introduced running from the latest source? When did you have the option to unchecked that option?
|
I didn't, but you posted a screen shot that indicates I will have the ability to uncheck the option.
Quote:
Originally Posted by BetterRed
. . .
Why would anyone want introduce a custom column with the same Column header value as a built in column's Column Header value — other than "Because you can".
Quote:
Originally Posted by DNSB
Sorry but I have to disagree there. Again, do you have any evidence that Kovid Goyal was aware of the existence of the Pages column header used by the Count Pages plugin?
|
|
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
Quote:
Originally Posted by DNSB
As for changing the Column header value for built-in columns? That way lies madness.
|
Why?
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.
BR