View Single Post
Old 10-22-2020, 05:02 PM   #40
geek1011
Wizard
geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.
 
Posts: 2,808
Karma: 7423683
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
Quote:
Originally Posted by jgoguen View Post
I suspect the high CPU process will be the Adobe ePub renderer or the ACCESS KePub renderer. If that's the case (assuming the info is accessible to NickelMenu scripts) it might be better to note which book is in use and the book position at the time and only note the process if it's not one of those.
That would be more something for NickelDBus (think NickelMenu, but for usage by scripts rather than the user). It's not currently supported, but since NDB keeps track of the current ReadingView for currentView, it wouldn't be hard to also make it return the book's URI.
geek1011 is offline   Reply With Quote