Two fixes from NuPogodi
1. ATM, the footers in selectmenu.lua & helppage.lua are left-adjusted,
these also contain the prompt for users how to call help
(selectmenu.lua) and how to go back (helppage.lua). By minor correction
to function DrawFooter() in filechooser.lua, one may readily make the
rest footers to look in a similar way.
2. When writing the code of inputbox.lua, I (NuPogodi) left the wrong
command to delete the 1st entry in the math function list
(called in calculator mode by pressing Alt-M).
Merge pull request #340 from tigran123/master

Two fixes from NuPogodi
Merge remote-tracking branch 'upstream/master'
Merge remote-tracking branch 'upstream/master'
ZOOM_FIT_TO_CONTENT_WIDTH_PAN pan centers page

When we start panning up in fit to width mode, we shouldn't
center page vertically on screen.
Merge pull request #342 from dpavlin/ZOOM_FIT_TO_CONTENT_WIDTH_PAN

ZOOM_FIT_TO_CONTENT_WIDTH_PAN pan centers page
Merge remote-tracking branch 'upstream/master'
don't preCache in two column mode

This also cleanups code to make it easier to follow chaning logic
a bit to generate useful Debug messages
Restrict the values of rcountmax to the range 0-10
Currently the user can enter any value like -10 and it is accepted and
saved in the settings file(s).
Don't allow floating point values for rcountmax
This is a better version of the previous commit, which:
a) makes the code more readable
b) disallows rcountmax values like "6.05", i.e. restricts to integers
only.
Merge pull request #344 from tigran123/master

Restrict the values of rcountmax to the range 0 to 10.
Merge pull request #343 from dpavlin/preCache

don't preCache in two column mode
Build mupdf in release mode, not debug.
Thanks to NiLuJe who pointed out that we are building mupdf in debug
mode. Switching to "release" build reduced the size of the kpdfview
binary and did not cause any performance degradation (but no noticeable
improvement either --- the page handling times seem to be exactly the
same, i.e. fluctuating a couple of ms in both directions).
ARM-specific optimizations
Thanks to NiLuJe who pointed out that our generic -march=armv6 can be
replaced (for K2/K3/DX/DXG) with a more specific optimization:
-march=armv6j -mtune=arm1136jf-s -mfpu=vfp. This I have now done and
also passed ARM_CFLAGS value to CXXFLAGS which is then passed to
crengine build. Tested, works fine. The performance improvement is
negligible (a few ms per page, but seems to be consistently better, i.e.
not just plus/minus fluctuations).
Enable LTO for kpdfview and crengine
Enaling link time optimizations for kpdfview binary and crengine library
causes another slight performance increase --- almost negligible (1-2ms
per page) but still noticeable by precise measurements.
reset last_globalzoom_mode on setglobalzoom_mode #346
Merge pull request #347 from dpavlin/last_globalzoom_mode_invalidation

reset last_globalzoom_mode on setglobalzoom_mode #346
Merge remote-tracking branch 'upstream/master'
Be minimalistic wrt LDFLAGS
Passing CFLAGS and LDFLAGS to kpdfview link stage has no effect in our
particular case, so I ripped it out, leaving it only for the crengine.
Merge pull request #345 from tigran123/master

Build optimizations.