[Kai771]

@dave2008
Thank you very much for giving me pointers. Before I decided to use a workaround that ended up in prerelease.2, I did take a look at the code of KPV new_ui_code branch. I then tried to replace screen.lua, and use the version from new_ui_code in LBR. That was probably too naive of me. It did start and worked fine on my K3 - until I tried to use rotation. Using rotation left me with a garbled up screen and I had to do a hard reset . I then decided to use the above mentioned workaround for the time being, especially with my history of missing stuff . Thanks again for pointing me in the right direction. I will try to sort it out when I have some more time.

@Iñigo
Hi, and thank you very much for taking the time to test LBR again. I really appreciate your comments.

Tested .2 in my K4NT.
It starts perfectly now.

I'm really glad to hear that. If I could trouble you some more, I'd like to ask you to check if my instructions for starting it up using cr3runner are valid. I have no idea if it would work. I think it's very important for people who are not as savvy as you are to have a simple way to make it run.

- I can change font familiy, font size and spacing. But all this information is stored per file not globally. I would prefer global settings

You can make font choice global. When you choose "Set document font as default", the current font will be saved as default font and used for new documents that you open (the ones that were not opened with LBR before). However, only the font is saved. Font size and line spacing are not. This is how KPV handles it. I'm not really familiar with it, there might be some reason why it is this way (like, idk, maybe it uses values specified in epub/fb2 files?). But I'll look into it eventually, and try to make it configurable.

- Compared with cr3, I miss the small topbar with info about time, battery level and, specially, the progress bar with marks per chapter (see screenshot in [1]). And the fullscreen mode. Going to menu -> Info is not as fast, and I like seeing this info on screen

I'm not a big fan of having info always on, but I do agree with you that going to menu -> Info is pretty slow. I did actually want to implement a shortcut for it, something like keyboard key, then up - but since I don't have K4NT, I couldn't test that and don't know if it will work, so I decided to stick to keys that I can test for the initial release. If you don't mind testing some more things, there are other things I'd like to put on K4NT specific shortcuts. (There are a lot of key shortcuts for K3, since it has a lot of keys . I'm saying this because I think you're unfamiliar with KPV, since you don't have K3, judging by the Device field under your name.)

- As in cr3, it would be nice to make cursor up/down mapped to prev/next section/chapter

Up/down are used for panning. Maybe some other combination would also work (keyboard - left/right? keyboard - pg_fwd/pg_bck?). Can someone tell me if keyboard key on K4NT can be used as modifier key (like alt)? Probably not, but I thought I'd ask anyway. Is it just like any other normal key, that returns code 29?

- Lines at bottom or/and top are cut

Yeah, I see what you mean. It doesn't look nice, but still, nothing is missing. You don't really need to read the last line on the screen, that isn't fully visible. When you press pg_fwd, that line will be fully visible on top of the screen. It may be helpful to also turn on overlap to help you find the line boundary easier (it's off by default in LBR). This is how KPV handles rendering of the page. As stated earlier, LBR is a fork of KPV. Meaning that it practically is KPV with a different user interface. I'm not really a developer, I'm just a noob. Really. Some changes to the user interface is the best I can do. Handling of page rendering, caching and all that serious stuff is out of my league. I do agree with you that it would be better to have only fully visible lines, but I'm afraid I can't do anything about it.

Regarding screen rotation: starting app in landscape shows app in portrait mode, but after quitting program, screen got scrambled and I needed a hard reset.

It behaves just as I expected. LBR (as well as the newest version of KPV) forces portrait mode in FileChooser and on document close, since we believed that landscape mode in FileChooser is pretty much useless on K3. In LBR, this can be disabled setting DFORCE_PORTRAIT to false in defaults.lua. But, in that case, on K4NT, you would need to be careful to exit LBR using the same orientation you used to start it, since Kindle framework won't be happy if you don't, as you already experienced . Let's file this as "Known bug" until I fix it using dave2008's suggestion .

Looking at your picture of CoolReader 3, it does look really nice. Top bar aside, LBR/KPV can't display footnotes like this. LBR/KPV's forte is pdf/djvu (especially since chrox added reflowing). And if I may say, there's nothing better for reading manga on Kindle (but that's my personal opinion )