Originally Posted by reader42
Well the only thing that needs to be done, is adjust the keymaps.ini
The idea is, that you connect the keys (KEY_*) with the actions ( DCMD_*, MCMD_*, CMD_* )
So if the Down-Key should got to the next page (in the "main"-view aka the book itself) you write in the [main] section:
KEY_DOWN = DCMD_PAGEDOWN
or to jump 5 pages
KEY_DOWN = DCMD_PAGEDOWN, 5
Today I can't experiment, but I definitely will later.
(I shouldn't even be sitting at the computer at the moment, but how can I not to? ;-) - the doctor was quite strict, I feel much better now anyway
are keys in a 5-way "D-pad"
with KEY_OK in center, used as enter or as menu access key.
KEY_BUTTON1 and KEY_BUTTON2 (or perhaps KEY_NEXT and KEY_PREV accordind to header files in SDK) are the two big page-turning keys.
Default keys for turning pages in FBReader are
KEY_RIGHT and KEY_BUTTON1 for page forward
KEY_LEFT and KEY_BUTTON2 for previous page
KEY_DOWN and KEY_UP are used to increase and decrease the font size in FBReader.
The menu for setting reading application options is operated by KEY_OK
(This is different from your menu. Because what you call menu is in fact Library view)
If you need to test something (like non-public beta, or some setting), do not hesitate to contact me.
By the way. It is absolutely amazing how you can do any development *at all* with the level of documentation in SDK. I was looking at header files to see how the buttons are called in PB360, and it is awful. There are quite a few #define statements for KEY_[SOMETHING] present that obviously have no corresponding hardware buttons in any device, without any explanation.
The only document, *in Russian*(!), in /doc/ directory merely states that there is no documentation and that we should see usr/include/inkview.h file. They didn't even bother translating this 30 line file to English [/rant mode].