View Single Post
Old 12-18-2018, 12:58 AM   #24
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,908
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by BetterRed View Post
Yeah - custom columns feature heavily in GUI plugins, but IIRC they don't feature at all in Metadata Source plugins. But they have configuration panels so that's where you'd allow the user to specify them - should be no need to delve into the arcane world of Plugin Tweaks.

But, but, but -- can a Metadata Source plugin even write to custom columns. The fact that none of them do makes me wonder if it is because they cannot. David and/or Kovid would know.
That's the thing. The metadata source plugin doesn't actually update the library. It extracts the details and passes them back to the metadata download process. That merges the results and presents them to you. After that, the library is updated. I do not believe this will handle custom columns.


Edit: Should have refreshed before posting.
davidfor is offline   Reply With Quote