View Single Post
Old 02-14-2021, 10:24 PM   #18
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,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by NiLuJe View Post
^^.

I was mainly hinting that UNCaGED is already taking a leap of faith by throwing SQL at Nickel at runtime at the end, so if Calibre were to join the fun by screwing with that *in the middle* of UNCaGED's run, "fun" things could start to happen ^^.

Of course, as you said, the whole point is moot, because direct file I/O is not happening ^^.
From memory the wireless driver doesn't actually see the disk, only what the application at the device end presents to it. If that is correct, the Kobo Utilities plugin would not be able to see the database. And the device end of the system should be able to set the series and other info.

But, at the same time, the wireless device should be able to present whatever information is available. I believe that Calibre Companion will return the reading status. Though I haven't looked at how that gets used on calibres side.
davidfor is offline   Reply With Quote