View Single Post
Old 12-14-2017, 09:24 AM   #16
DaltonST
Deviser
DaltonST is the One.DaltonST is the One.DaltonST is the One.DaltonST is the One.DaltonST is the One.DaltonST is the One.DaltonST is the One.DaltonST is the One.DaltonST is the One.DaltonST is the One.DaltonST is the One.
 
DaltonST's Avatar
 
Posts: 1,500
Karma: 101298
Join Date: Aug 2013
Location: Texas
Device: 8" Win10 Tablet w/Calibre64
Quote:
Originally Posted by Gary_M_Mugford View Post
You're not wrong. I surrender. Thanks for taking the time to create this. GM

NOTE: And we both know Kovid will respond somewhat ... negatively ... to this request given it's ... lack of common need.

It is a common need as of 2016 when he added "plain text" and "short text" as "virtual datatypes" to Calibre. However, he still thinks of them just as "comments", which is the "official" datatype. That is one of the consequences of not using 3d-normal form database design with Custom Columns. Further, his previously stated logic for not adding them to Bulk Metadata Edit (BME) conflicts with having INT, FLOAT and BOOL datatypes supported. His logic of not supporting "plain text" and "short text" is that they are "book dependent". Guess what; so are INT, FLOAT and BOOL. If he is being intellectually honest, he should not allow #pages or #read_already to be set simultaneously for a group of books in BME. However, he has the final say in the matter. Hence, my GUI Tool.



DaltonST
DaltonST is offline   Reply With Quote