In another thread several people have commented on a bug in the PDF-Reader of the M92. The keymapping of the joystick, so that you can use the joystick for page turning, doesn't work properly when custom margin settings are used.
I use the most recent firmware and the most recent pdf-reader patch with the odd/even margin settings.
Several people have confirmed the bug and it is very annoying. I'm a right-handed person and I use the M92 mostly in the leather cover. That means that unless I don't use the the stylus, the joystick on the right is the most natural way to turn pages. (Yes, besides the "<" and ">" buttons swiping with the stylus works properly for page turning.)
With standard settings for margins (without any custom margins) page turning with the joystick is ok.
Here is a description of the bug from another thread:
https://www.mobileread.com/forums/sho...d.php?t=201694
BUG report(s) PDF Reader v2013.01.02
Quote:
Randy11 wrote:
Bug 1.8 (1.8.20121113) + PDFReader_Patch 2013.01.02 : PAD/Key mapping => Page turn
Hi,
I've a bug with the PDF Reader (last patch) when I use the key mapping for the PAD. This is the actions to do to see my bug :
Load the PDF file, I use "tabularx.pdf" but I've the same problem with other files
Page Settings : Clear Margins
Page Setting : Universal Manual => PICTURE 1
=> I get the PICTURE 2
Tools : Key Mapping -> Page Turn
Change page with the PAD => PICTURE 3
It takes 2 press on the PAD to see one page, then only one press of the button ">" is necessary and the page is fully displayed.
With the PAD, the first press show the full page and the second seems only to move the viewport.
This bug was confirmed by Vaa, thanks to her/him
Feher wrote:
I am experiencing the same bug.
Earlier page turn was working fine even in two point zoom mode but now page turn moves the viewport instead.
|
In that thread there are also photos that explain the problem better.
This is the problem:
Quote:
It takes 2 press on the PAD to see one page, then only one press of the button ">" is necessary and the page is fully displayed.
With the PAD, the first press show the full page and the second seems only to move the viewport.
|
With the ">"-button one click turns the page. With the stylus one swipe turns the page. But with the joystick, you need two clicks. Because the first click inexplicably only moves the viewport a little bit. Instead of turning the page. Only the second click turns the page. Very inconvenient, and I'm sure that's not the way it is supposed to work.
With standard margin settings (without any custom margin settings) the joystick turns the page at the first click, just as you would expect it.
And it doesn't matter which method I use for margin setting:
Custom Margins or Two Points Margins from the regular PDF-Reader, or
Universal Manual and Odd Even Margins from the new patched (Beta-)PDF-Reader.
All methods produce the same bug.
And yes, I have explicitly switched the keymapping of the joystick so that it should turn pages. But it doesn't.
Here's another forum member from the German subforum with the same complaint:
https://www.mobileread.com/forums/sho...=171810&page=4
Ausführlicher Erfahrungsbericht: Boox M92 (9.7 inch Reader)
Quote:
alegst wrote:
Ein kleines Manko habe ich allerdings festgestellt. Wenn ich ein PDF Buch lese, welches ich auf größer als 100% stelle, kann ich mit dem Jostick nicht mehr blättern. Das ist schade, da man dan quasi immer nur die linke Hand benutzen kann. Vielleicht gibt es da Abhilfe.
|
So zooming seems to produce the same problem. But when I tell the PDF-Reader via keymapping that the joystick should be used for turning pages, it should do just that, and nothing else.
At the very least if I tell the PDF-Reader to fit the viewport under "Reading" => "To Page".
Zooming is not the problem, since the proper way to hide the margins is via margin setting and then setting the viewport via "Reading" => "To Page".
With this setting the joystick should never shift the viewport if keymapping of the joystick is switched to page turning.
Unfortunately you have never commented on this bug.
Booxtor, could you please
- confirm this bug
- tell us if something can be done about it
- if / when we can expect a fix / patch
This bug cannot be particularly difficult to fix: After all, button X must only do what button Y can already do. And according to some posters it already worked in previous versions.
It seems to be a relatively old bug, it probably affects the majority of users, since it affects a very basic mechanism, it's annoying, and it should be easy to fix.
If you could fix this / provide a patch, you would make a lot of people happy
(And I bought my M92 from your store.)
