When the the power_off switch is pulled a empty SYN_REPORT is generated and koreader crashed on a DEBUG line.
The DEBUG lines now generate identically spaced output, which makes it easier to read by eye.
use `self.highlight:handleEvent(Event:new("Tap"))` instead of
`self.ui:handleEvent(Event:new("Tap"))` when clearing highlighted
text since Tap event in latter situation will be captured by
the dogear widget.
While debugging ```GestureDetector:panState(tev)``` I saw that the TRACK ID never had -1 values .
So back to debugging ```input.lua```.
Now the Kobo Aura can pinch and expand.
/luajit: ./frontend/ui/gesturedetector.lua:84: attempt to concatenate field 'y' (a nil value)
Hopefully the use of the "," in the DEBUG function instead of the string concatenate operator gets rid of it.
without the height of the close button widget
This will make room for one more menu item entry and fix#355 and #394.
The larger tap zone for close button widget is still there.
the Kobo framebuffer comes up in landscape mode, that is, landscape
in the other direction as we do it when going into landscape mode.
we leave it this way, and rather allow for a rotation correction at
framebuffer setup.
this PR pulls the relevant changes from koreader-base and makes the
screen code aware of this additional rotation setting.
Kobo framebuffers should now work properly with the new framebuffer
FFI code. They can stay in 16bpp mode and don't change the current
framebuffer settings. They should thus properly interoperate with
the native framework on Kobos as well as sergeys KoboLauncher
(no garbled screen when returning)
Screen.width and Screen.height are now gone, use the methods
getWidth() and getHeight() to get the relevant data. They will
take blitbuffer/framebuffer rotation into account.
We can get rid of shadow blitbuffers. Screen.bb is now fb.bb.
All bpp conversion is now done by the blitbuffer abstraction layer.
Rotation mechanism is adapted to this.
