David

@NiLuJe could you look at this as well, seeing as you're being quite helpful ;). I don't really want to mess with sensors i am not familiar with...

Current state of affairs: Left/Right keys have been repurposed to 'Previous/Next Chapter' (on both readerrolling and readerpaging) -- Previous behaviour here was redundant 'Previous/Next Page' (this change seems inoffensive to...

> Panning behavior isn't really the right word. It simply goes per screen height instead of per page. My point isn't that you can't change things since the screen height...

For reference, I am posting this here https://github.com/koreader/koreader/issues/4329#issuecomment-437702481 since I keep going on about how wonderful the button mapping on stock kindle is, for those unfamiliar with it > The...

> I don't believe that's what it's called in the code. Panning is the act of arbitrarily panning, not the act of turning a page in continuous/scroll mode. Oops, yes...

> > As of now, that is the case. > > > > But what about the dictionary lookups and highlighting? The point is it should be properly usable while...

> > What i was thinking was, to match the changes for readingpaging with those of readingrolling (up/down calls content selection) and to reassign the page turn ones to what...

> Anything that randomly skips stuff isn't working properly. But that is just the way it works currently. > If we assume that page up/down is the primary entrance point...

> > I am running it on mine and works great, (with pdf) page turn buttons move to bottom bit on first press, then turn page on second press. Up/down...

> > I know, but I would not map them differently as it matters to some (including me) to be able to hold the device with either hand. > >...