PocketBook-KOReader: a document reader for PDF, DJVU, EPUB, FB2, CBZ, ... (AGPLv3)

[Frenzie]

I was at a complete loss as to what you meant until I went to look at the statusbar settings.

Anyway, long-press it.

[igorius]

@Frenzie: Now I was lost! But then i tried that long press at settings/status bar/custom text....

Thank you very much!

[igorius]

Status-bar bugs: Font size of the bottom status bar is 13, to get the same size for the upper status bar, i have to set the font size there to 28.
Other bug found: The upper status bar disappeared when i opened a new book and i cannot get it to appear again...

[NiLuJe]

#invalid, the two bars are separate because... they're separate .

(The top bar is mostly entirely out of our control, it's rendered by CRe, unlike the bottom one).

You can toggle the top bar via the final tab of the bottom menu, IIRC (and, again, long-press to set a default; reading the quickstart guide helps ).

[igorius]

Originally Posted by NiLuJe

#invalid, the two bars are separate because... they're separate .

(The top bar is mostly entirely out of our control, it's rendered by CRe, unlike the bottom one).

You can toggle the top bar via the final tab of the bottom menu, IIRC (and, again, long-press to set a default; reading the quickstart guide helps ).

Äähm, what i want to say that same size of font should be same size everywhere! But here to get a height of say 6mm, i set bottom to font size 13; top bar to 28, which is more than double of size!

Ok, i found the button at the bottom menu, even when i found it only because i had to set the font size of the book. So, normally i would never look at the bottom menu to get the upper status bar set!
And i find it a bit confusing on how things are named... I have set language to german, to be able to understand what things coud eventually mean. My english isnt good enough.
And yes, i have read the manual, but didnt memorize all. Its far too much to get everything at same time (not your problem, i know, but want to explain it)

PS: Whats CRe?
What means #invalid?

[zmix]

I updated my Pocketbook Era from KOReader 2022.07 to 2022.08 by replacing (rather than "merging") the app and folders on the device with the app and folders in the download.

Oops.

Lost all of my preferences, and none of my dictionaries are available.

What is the correct way to update?

[zmix]

Why does the KOReader app appear twice in my Pocketbook's "USER'S" section?

It appears as :

@._koreader

and as:

@koreader

[pazos]

Originally Posted by zmix

Why does the KOReader app appear twice in my Pocketbook's "USER'S" section?

It appears as :

@._koreader

and as:

@koreader

https://www.mobileread.com/forums/sh...4&postcount=15

[ldmobi]

Is it possible to quickly disable/enable touchscreen (with a gesture, for example) or quickly disable/enable highlighting?


I use my Pocketbook inkpad 3 to read both fiction and non-fiction. My problem is that while I like to highlight non fiction books, I read fiction in bed, and I never highlight it.



So basically I have two scenarios:
1. Highlight enabled
2. touch disabled, no highlights (so that I can hold the reader with a thumb resting on the screen, without triggering highlights or page change)

I switch between the two frequently (I usually read a fiction and a non fiction book at the same time) and going into the menu and disabling/enabling highlighting every time I switch is annoying.


At the moment I'm using the pocketbook own reader to read in bed because the Inkpad 3 default reader can disable the touchscreen with a double click of one of the buttons (you change page only by buttons then).


I can imagine the following solutions:

- One way would be assigning a long press toggle (do nothing/highlight) but at the moment I only see the option to cycle highlight action

- Another would be to implement touchscreen disabling using a button, this would be optimal, because would allow carefree handling of the reader in bed, without fear of accidentally turning pages, which is important, when reading to relax.

- Another could be disable/enable touchscreen inputs with a gesture.


Is there anything I'm missing to solve my problem using the current version?

[NiLuJe]

The framework to do both of these things are there, but nobody's bothered to actually tie the two together .

[ldmobi]

Originally Posted by NiLuJe

The framework to do both of these things are there, but nobody's bothered to actually tie the two together .

Unfortunately I haven't the skill to do it myself.
Do you think would be useful to open an issue on github as feature request?

[NiLuJe]

It'll have a much better chance of not being lost to the sands of time that way, yeah (check first: there might actually already be one).

[VladimirS]

If I may, I have question for developers of KOreader,
and from other knowledgeable persons...

Does Koreader software depends on Pocketbook's
firmware, or Koreaders uses resources of underlying hardware
independently of device's firware...

I am asking this because I don't know how
is performance (opening and reading of various ebook formats)
better (faster, more responsive) on Koreader than
on default ebook reading app (default Pocketbook app).

Just turning book pages, up and down. maniplulation with
interface, looking up word in dictionary, opening of
table of contents, opening of bookmarks ...All
action appear more responsive.

I know answer is complex, we needjust some hints if you can give to us

Thank you very mach for your answers and keep a great work

[pazos]

Hopefully the answer is simple:

They behave differently because they're very different programs.

The same things that make KO faster than PB reader in your examples make KO slower than PB in counterexamples, such as changing font face or font size in an epub.

Some more general info:

- KO is always constrained by hardware/firmware.
- Porting KO to a new platform involves porting input (buttons, touchscreen...) and ouput (screen drawing, epd updates) handlers.

- Some platforms, like Kobo or Remarkable expose a very generic interface at the firmware level and everything is implemented into a big blob (a.k.a stock app)

- Other platforms, like Pocketbook or Android, restrict low level access to these interfaces and provide a middleware to interact with.

As a rule of thumb platforms where we have raw access to generic input events & generic framebuffer can be optimized much more than platforms where we deal with middleware.

An extreme example of these differences is in partial refreshes: almost everywhere we can choose the waveform used to refresh the screen and adapt it to our tastes (i.e: increasing speed by loosing some quality if the rectangle we're going to draw is small or its content not so important).

That's not the case on Pocketbooks, where the middle man decides for us.

[zmix]

Adding to the above response, I've noticed that KOReader 2022.08 is much faster in certain tasks than 2022.07 was, particularly button presses related to highlighting text.