View Single Post
Old 09-20-2020, 01:13 PM   #11
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 6,985
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
I agree with compurandom that search about 'column' like ondevice but containing a name for the connected device would be useful thing to have.

Unfortunately, grepping through the calibre code, there are a lot of places where 'ondevice' gets special treatment. Adding a new pseudo column would touch a lot of stuff.

Alternative idea: Is there, or could there be, a template function that returns a device name? Then a custom column-from-columns could use the function to make it available in searches?

compurandom: Is this all about device specific SmartEject searches, or do you have other use cases as well?
JimmXinu is offline   Reply With Quote