CoolReader3 Fork

[brucelee]

Originally Posted by LittleBiG

Ah, yes, sorry. I tried 3 pairs, they worked. Thanks!

Great.

Originally Posted by j0r13n

There seems to be a refreshing bug.
When a pageturn is processed IMO the following happens:

- step 1: the new page is displayed inverted
- step 2: just before step 3, the old page is displayed inverted
- step 3: the new page is displayed normal

So IMO step 2 should be skipped which will result in a slightly more crisp display with more consitent black text and also better contrast

Regarding the full page refresh thing.. I don't see anything wrong with it.
It's used like this:

PHP Code:


// Draw image buffer
draw(0, 0, _front->GetWidth(), _front->GetHeight());

// Show image on screen
FullUpdate(); 


I've tried simulating what you want but it's moving way slower and it's ghosting:

PHP Code:


// Invert buffer
InvertArea(0, 0, ScreenWidth(), ScreenHeight());

// Show inverted image
PartialUpdate(0, 0, ScreenWidth(), ScreenHeight());

// Draw page buffer
draw(0, 0, _front->GetWidth(), _front->GetHeight());

// Show page
PartialUpdate(0, 0, ScreenWidth(), ScreenHeight()); 


So I'll just leave it as it is. I seriously don't see anything wrong with the screen update.

[LittleBiG]

Originally Posted by brucelee

Regarding the full page refresh thing.. I don't see anything wrong with it.

You are lucky. I suspect the problem affects only the Pearl display (TL2) and probably you have Carta (TL3). On my TF2, after just one page turn with fast update, the text will lose its contrast and crispness, the letters immediately will be "hairy".

[LucyOne]

Originally Posted by LittleBiG

You are lucky. I suspect the problem affects only the Pearl display (TL2) and probably you have Carta (TL3). On my TF2, after just one page turn with fast update, the text will lose its contrast and crispness, the letters immediately will be "hairy".

I can test that on my TL2. What are your settings? On mine refresh is working as it should.

[brucelee]

Originally Posted by LittleBiG

You are lucky. I suspect the problem affects only the Pearl display (TL2) and probably you have Carta (TL3). On my TF2, after just one page turn with fast update, the text will lose its contrast and crispness, the letters immediately will be "hairy".

TL3 has that ghosting effect too, but I don't really mind it

I prefer using non-antialiased text without full updates. If the screen doesn't feel right at some point, I just trigger the "Full screen update" tap action.
(Don't get me wrong. I switched to antialiased font with full updates every 5 pages for the tests)

I'm quite comfortable using Bookerly 32px without antialiasing. Page turns are really fast too.

[j0r13n]

This isn't about the Carta vs Pearl display or full vs fast screenupdate.
It's about a small malfunction in the full screen update procedure in Pocketbook.
So it's not a Coolreader bug; it's also reproducable at the build-in Adobe and FBreader.
And it's a minor issue but nevertheless excists.

Personally, I prefer quality vs speed.
And speed is a relative term; an user invention is still necessary to 'turn' a page.

You can exhibit the phenomenon yourself:

Make sure you have backlight on at max setting and set 'Display update mode' to 'Don't use fast updates'.
Choose a dark, bold font and set it's size at max (nowadays you can get to 150 and perhaps even embold the font even more (Font settings -> Font embolding). Now start turn pages and look accurate and you can exhibit some light ghosting from the previous page in the dark portion of the text.

When you carry out the same experiment and set 'Display update mode' to 'Always use fast updates' and manually refresh after a turned page (program either 'Full screen update' or 'Invert display' as a Tap action) and you will witness a more even, darker black text.

Although not a lot people will read with this font settings, this phenomenon will still be present at smaller sizes and to put it plain simple: the contrast on a Pocketbook could be a notch better.

As earlier said, it's due to how Pocketbook executes a full screen refresh at page turn:

- step 1: the new page is displayed inverted
- step 2: just before step 3, the old page is briefly displayed inverted
- step 3: the new page is displayed normal

Look at the pictures in the attachment (build-in Adobe reader) to see wath I'm try to explain...

[brucelee]

Thanks for the explanation and pictures. I really appreciate. Unfortunately, I think this can't be fixed.
1. It's a system function and I have no idea what's behind it. It might even directly call some driver function (maybe the display is programmed this way)
2. I've tried recreating the full update function and, as I already said, it's not ok. Lower quality and speed.
3. It might actually not be a bug. Maybe that's the way it should work.

[brucelee]

v0.0.6-17-43:

- Set default skin according to the firmware and screen resolution (for fresh installs)
- Dictionary tries matching case sensitive before case insensitive
- Fixed dictionary not translating words when the dict dialog was positioned at the top
- Fixed touch event being ignored after deleting citation
- Cite: Default selected button: Choose paragraph

[j0r13n]

brucelee wrote:

It might actually not be a bug. Maybe that's the way it should work.

Examined a Kobo Glo - with Pearl screen - and is showed something remarkable...

It exhibits almost the same behaviour with a full screen refresh - briefly displaying the previous page - only with the Kobo Glo, instead of showing inverted, it shows up normal. This translates to a more consistent, dark text but at the cost of ghosting the previous page in the light portion of the displayed page. Well, I prefer the Pocketbook way

Still, I find it strange behaviour.

If it just was possible to program a full screen update AFTER a new page actually is displayed...

Thanks again for all the effort, you're the sole reason to buy a Pocketbook!

[brucelee]

Originally Posted by j0r13n

If it just was possible to program a full screen update AFTER a new page actually is displayed...

Here's a dev build containing this change: #ed1a3e0/builds/626/pro5/latest.zip
It doesn't feel right though.

[druss67]

Hello,

the function "follow the link" in a book seems for me not working.
When I select this function, the link is underlined and a pop-up appears in the top of the screen.
The arrows are white and I can do nothing more, only close the pop-up with the cross.

I suppose the right arrow must be black, and permits to go to the link, no ?

Or perhaps I missed something...

[LucyOne]

Originally Posted by druss67

Hello,

the function "follow the link" in a book seems for me not working.
When I select this function, the link is underlined and a pop-up appears in the top of the screen.
The arrows are white and I can do nothing more, only close the pop-up with the cross.

I suppose the right arrow must be black, and permits to go to the link, no ?

Or perhaps I missed something...

Have you tried tapping the link after the arrows on top appear?

[j0r13n]

Tried the dev build, thanks for the effort!

Too bad the previous page text becomes apparent at the inverse stage (see attachment) of the full update and will leave traces after the final proces has finished.

When I tried to repeat the proces manually I didn't get the ghosting issue at first but when reducing the time - between a (fast update) page turn and a manual screen refresh - as short as possible resulted in identical ghosting effect.

It looks like the full update executes to soon and must be delayed for best display quality.

Somewhere between 100ms and a full second exist the holy grail

Brings a whole new meaning to the 'Don't use fast updates' phrase! LOL

Maybe it's possible to add another item to the Display settings: 'Full update mode' (normal/delayed) as the 'Full update after x pages' will also benefit.

As a side note: it's only to squeeze out that last bit to slightly higher quality text, so if it's to much trouble; don't even try!

BTW, the Settings menu is currently prone to less optimal readability as it's inherits to much settings which should IMO only be carried out to the reading part

Thanks again for your efforts!

[LittleBiG]

Hi, thanks for the bug fixing release. Additional thanks for the cite default, it feels so smooth now.

I would like to suggest two small things:
1. The directory window doesn't have a margin on the right side. It would not be a big deal, but when the last word in the row is italic type, the half of the last letter is out of screen.
2. I would appreciate a small frontligth indicator in the status bar. (Like the bulb in the original firmware.) Sometimes the frontlight stays on accidentaly in the morning after reading at night. I can notice this only if I open the menu and I can see the bulb there.

[LucyOne]

Originally Posted by LittleBiG

2. I would appreciate a small frontligth indicator in the status bar. (Like the bulb in the original firmware.) Sometimes the frontlight stays on accidentaly in the morning after reading at night. I can notice this only if I open the menu and I can see the bulb there.

I second that!

[LittleBiG]

Yesterday evening I forgot to switch off my TL2, I left it in Coolreader, the brucelee standby mode. Now in the morning I realized that the battery charge dropped by 40 percent Is that ok? Coolreader uses that much of battery even if it is just simply opened??