-
Notifications
You must be signed in to change notification settings - Fork 23
Description
The first time I set up my 8bitdo zero 2 a year, I remember that prevChapter and nextChapter worked as METHOD commands. I stopped using it with my Kobo Sage for most of the past year, and decided today to re-set it up. I have prevPage and nextPage working correctly, but prevChapter and nextChapter does nothing on my Kobo.
Has something changed? Do prevChapter and nextChapter no longer work, or am I doing something wrong? I have tested by taking a config line where nextPage works and replacing it with nextChapter, and then tested on my Kobo and seen that nothing happens.
I looked on MobileRead threads and found this: https://www.mobileread.com/forums/showthread.php?p=4510632&highlight=prevChapter#post4510632
Regarding additional options beyond prevPage and nextPage.
I spent an inordinate amount of time looking at the btpt source code and decompiling the libnickel library. I don't code Qt so it was a big headache but I could at least make some guesses. a) it only uses ReadingView methods, b) the method needs to take zero arguments, and c) it somehow truncates the method name to about 12 characters when trying to call them. prevPage() and nextPage() are callable with btpt but most/all others aren't. goToPrevChapter() even requires an argument so unless it didn't at one time, it was never a valid option at least on the Libra 2. prevChapter() does exist in the AudiobookPlayer methods and that is probably where the confusion came from.
To make the fancier remotes like the 8bitdo work, it would probably require a new plugin that calls more than just ReadingView stuff. I have a notion of maybe hooking into NickelMenu/NickelDBus with an event listener similar to btpt but honestly I don't think I'll have the time to look into that this year at all. Remember I don't code Qt and it would be a huge time suck.