Quote:
Originally Posted by JSWolf
Does the refresh bug show up if FullScreenReading is never turned on? As I've never used that, it's never been on.
|
The bug is triggered by performing one of these actions from
within a book (from outside the book doesn't trigger it):
1. putting the device to sleep and waking it again.
2. using the dictionary
3. accessing the reading settings menu
4. accessing the table of contents
5. accessing the advanced font menu
6. maybe other things...
The bug can be un-triggered by closing the book (return to library or homescreen.)
Once triggered There are two parts to the bug on devices other than the Aura:
1. Full refresh every page regardless of refresh rate settings. It is a much heavier refresh than the normal page turn refresh.
2. An extra refresh when tapping the centre of the page to open the reading menus.
The first part only happens in full-screen mode (FullScreenReading=true and "Show header and footer" unticked.)
The second part happens in normal reading mode too, even if the FullScreenReading feature setting is not in the config file.
(Edit: On the Aura the trigger conditions seem to be the sme, but instead of a refresh every page, there is no refresh at all. I don't know what happens on the Aura when bring up the reading menus.)
To see if it happens on your device (other than the Aura), just do this:
1. Open a book
2. Put the device to sleep (or one of the other trigger actions) and wake it up.
3. tap the screen to bring up the reading menus (header and footer icons)
If there was a refresh when you brought up the reading menus, then the bug has been triggered.
Edit: If you don't use full-screen mode and don't care about the extra refresh when opening the menus then the bug is no big deal, you might not even notice it. But if you are used to setting a very high page count between automatic refreshes and tapping the screen twice to refresh manually when needed, then the double-refresh that results is a bit annoying even in normal reading mode. In FullScreenMode the fact that the refresh after triggering the bug is an extra heavy-duty one means you will probbaly notice it even if you have set the device to refresh every page anyway.