[Nook Touch General] nmyshkin:
I'm pleased you are enjoying what I've done. I may not be able to solve all your issues, however. The problem with doing something like this is that everyone has their idea of the "perfect" reader and one person programming away in isolation can't possibly anticipate all those concepts. So the result is limited by that reality.

I never anticipated that someone would have two readers that both handled epubs, so what you are seeing is not surprising. For an epub, the "now reading" selection is determined solely for the stock reader. There is no code to search out other epub readers, so that's what is going on there. As you've probably discovered, FBReader has no auto-cover capture ability. I'm working on CWM flashing images for all the principal readers in anticipation of June 2024, and of all the choices FBReader is the only one that does not store any cover images at all. Manual capture (using the designated button) should "work" for FBReader but after that...I'm not sure. Let me install FBReader on my stock system and see what happens. I'll get back to you on that.

OK, so this is one of the complications that required making so many versions of SetCover. Every time you delete and remake the bookcover widget, the widgetID number changes. I don't know how to access this information so the only recourse is to find out the new widgetID number and then download the appropriate SetCover app. The old app must be uninstalled before installing the new version. The new app needs to be initialized by tapping on it and confirming SU access, then you're good to go again.

That said, the bookcover widget is not the problem. The problem is in the lack of coding for coexisting epub reader apps. Again, I'll check on this and see if there is something "simple" that might be done.

One last thing, sometimes in all the fooling around it is possible to get two files (or more!) in /media/NowReading/BookType. When this happens, the "now reading" button will select whatever kind of reader is associated with the first file in the directory. So you might want to look there and be sure there is only one file (1, 2, 3, or 4).

Edit: I've checked the behavior of FBReader with my current setup as shown in the first post. As expected, a manual cover capture works, placing the correct cover image in /media/NowReading and also /media/screensavers/CurrentBookCover. But because there is no association with FBReader in the NST UI app, the image never gets to the screen. That part, I believe, would be relatively easy to change, but the change would be in SetCover and that means it will be locked in to whatever widgetID number you have currently. One accidental deletion of the bookcover widget and you'll be dead in the water.

The other issue I foresee is that FBReader can also read mobi files (I think). That would conflict with the Kindle app. Of course you may not be running that. So....which readers do you have installed and is that likely to remain stable?

Edit, Edit: I've had some time to think about this while trying to wrestle with AlReader and I think it might actually be pretty simple. You picked the perfect alternate reader since FBReader does not store any bookcovers. That means cover capture must be manual (like for Kindle, EBookDroid and PerfectViewer) and that also means that the current book is opened by simply opening the app, not the actual file. So just a line or two in both NST UI and SetCover will add FBReader as an alternate reader for any type of book it can handle.

I'd be happy to do this for you, but I would need your current widgetID number and I would caution you to make a complete backup once you get things "settled". Wherever the widgetID stuff is hidden, it does end up in a backup, so that's one way to ensure these custom apps would continue to work in the event of an accidental deletion of the bookcover widget.

Also, I don't know whether you'd be interested in it or not, but while working on the FBReader edition of my new UI I created a tiny app that accesses the FB Library directly. This is what I have in the "Reader" SimiFolder so that it behaves more like the stock reader. The "reading now" function opens the app in default mode (reader) but the extra app allows you to just go to the library section (like for a new book). I can provide that app here if you're interested.