CoolReader3 Fork

[brucelee]

Interesting.

[TimKGS]

brucelee, in the dictionary by pressing buttons google or wiki browser opens only.
So it should be?
Can we hope for the opportunity to search selected words in these services?

P.S. many thanks for your work

[brucelee]

Hmm.. That's right. I didn't test this feature for a while. It seems like FW5.7 doesn't even automatically start WiFi when launching the browser. I think this might be a firmware related thing. It should still work fine with FW4.

[TimKGS]

Yeah, in FW4 I did not use a your CR, and FW5.5 behaved in the same way by tap buttons only run a browser.

[brucelee]

Originally Posted by TimKGS

brucelee, I think it is worth making exited StandBy not "touch", and the "swipe" as unlocking smartphones.
Get a full lockdown mode, instead of the standard, with the release without the help of the "power" button.
A top screen (cover) you can display a prompt that unlocks swipe.
How do you like the idea?

Thought about it a bit more.

I implemented this because I have a case for the reader and the device is set to turn off after 1 hour. So most of the time I just close the case cover and let it be. The stand by mode will turn off the light after 5 minutes and return to its initial state really fast when any input is received. So I'm not worried about unwanted input that may occur.

Now there's the situation you pointed out which seems to be necessary for those users not having a case for the reader. Well, a slide unlocker would be useful indeed but the problem is that it won't block all the buttons. The home button is system assigned and I can't override it through the app. That's because the event never reaches the app. Sooo basically, this isn't quite a real lock feature since pressing the home button still "unlocks" the device. I suppose the chances are not in favor of the button being randomly pressed but it can still happen and screw things around.

[TimKGS]

Originally Posted by brucelee

Thought about it a bit more.

I implemented this because I have a case for the reader and the device is set to turn off after 1 hour. So most of the time I just close the case cover and let it be. The stand by mode will turn off the light after 5 minutes and return to its initial state really fast when any input is received. So I'm not worried about unwanted input that may occur.

Now there's the situation you pointed out which seems to be necessary for those users not having a case for the reader. Well, a slide unlocker would be useful indeed but the problem is that it won't block all the buttons. The home button is system assigned and I can't override it through the app. That's because the event never reaches the app. Sooo basically, this isn't quite a real lock feature since pressing the home button still "unlocks" the device. I suppose the chances are not in favor of the button being randomly pressed but it can still happen and screw things around.

In principle, it is sufficient to block the screen. The buttons are pressed tightly.
Yes, and the current state is not clear - whether the device in stand by mode, or already off. On the screen in any case, cover and once again touching the screen to verify this. A bit uncomfortable.

[brucelee]

Fair enough.

[Revilo42]

Which zip I can use for the Pocketbook sense?

[ibat]

Hi Brucelee,

Would it be possible to make words in the dictionary clickable/selectable?
Use case: one needs to lookup the words used in the explanations.

[brucelee]

Originally Posted by Revilo42

Which zip I can use for the Pocketbook sense?

pro5 because your device has firmware 5

Originally Posted by ibat

Would it be possible to make words in the dictionary clickable/selectable?

Yes, that would be a nice feature. I thought about it too.

[brucelee]

v0.0.6-17-24

- Updated French
- Updated Russian
- Updated German
- Updated Romanian
- Updated Czech (84%)
- Updated freetype to v2.6 (changelog)
- Standby mode is used only for touch devices
- Added package readme

[gillesit]

The latest version pro2 does not work on my pb912, with this information: "Can not open the book. The book could be damaged or protected".
In italian :"Impossibile aprire il libro. Il libro potrebbe essere dannegiato o protetto".

Ciao

[brucelee]

Originally Posted by gillesit

The latest version pro2 does not work on my pb912, with this information: "Can not open the book. The book could be damaged or protected".
In italian :"Impossibile aprire il libro. Il libro potrebbe essere dannegiato o protetto".

Ciao

If v0.0.6-17-23 worked for you with the same ebook then it might be some problem caused by freetype v2.6. That's the only thing that can affect books. All the other changes were merely "cosmetics". The thing is that this would break all the builds since it's not firmware specific.
Sooo... Are you sure you've tried opening the same ebook with v23 and v24? If yes, are there other users affected by some similar issue?

[brucelee]

v0.0.6-17-25

- Updated Chinese

[gillesit]

Originally Posted by brucelee

If v0.0.6-17-23 worked for you with the same ebook then it might be some problem caused by freetype v2.6. That's the only thing that can affect books. All the other changes were merely "cosmetics". The thing is that this would break all the builds since it's not firmware specific.
Sooo... Are you sure you've tried opening the same ebook with v23 and v24? If yes, are there other users affected by some similar issue?

The version I use now is the 0.0.6.17-21-602 the last that works, before it was renamed PRO2.
ciao