View Single Post
Old 02-15-2018, 07:58 PM   #8
ilovejedd
hopeless n00b
ilovejedd ought to be getting tired of karma fortunes by now.ilovejedd ought to be getting tired of karma fortunes by now.ilovejedd ought to be getting tired of karma fortunes by now.ilovejedd ought to be getting tired of karma fortunes by now.ilovejedd ought to be getting tired of karma fortunes by now.ilovejedd ought to be getting tired of karma fortunes by now.ilovejedd ought to be getting tired of karma fortunes by now.ilovejedd ought to be getting tired of karma fortunes by now.ilovejedd ought to be getting tired of karma fortunes by now.ilovejedd ought to be getting tired of karma fortunes by now.ilovejedd ought to be getting tired of karma fortunes by now.
 
ilovejedd's Avatar
 
Posts: 5,110
Karma: 19597086
Join Date: Jan 2009
Location: in the middle of nowhere
Device: PW4, PW3, Libra H2O, iPad 10.5, iPad 11, iPad 12.9
Quote:
Originally Posted by theducks View Post
Not a good plan
That (and some others) field auto updates during the normal management of books.

Use a Custom field for stable data
A custom column is what I meant by "better to have a placeholder for file size". My main question was whether I need one custom column or two.

e.g.

#epub_size (int) - {:'select(formats_sizes(),'EPUB')'} set via bulk s&r
then number formatting done via display formats option (is that doable?)

or

#epub_size (int) - {:'select(formats_sizes(),'EPUB')'} set via bulk s&r
#size (composite) - {#epub_size:human_readable()}
ilovejedd is offline   Reply With Quote