View Single Post
Old 10-05-2016, 03:15 AM   #6
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,773
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by TheMadGuy View Post
Partially that's a nice idea. I thought about those custom fields several times and used them for a while, but whenver I get something new, there is a lot to modify. That was the reason for me to write this in the hope to implement those custom fields as standards
A snowflake's chance, the database hasn't been changed for several years, if it were to change millions of users would be affected. A lot of thought went into making it extensible with custom columns

Quote:
"...but whenever I get something new, there is a lot to modify."
Do you mean a new book or a new column? It's easy to go overboard with adding extra columns.

I prefer to edit through the book list, where I can order the fields to suit what I'm doing. If you prefer the dialogue boxes - try the different layouts in Preferences->Behaviour->Metadata Edit (single) layout options and have a look at Preferences->Tweaks->Order of custom column(s) in edit metadata

BR
BetterRed is offline   Reply With Quote