View Single Post
Old 02-20-2015, 05:49 PM   #81
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@gong: Amended my previous comments, because of course we do see the effect of KSM's viewport shift on such a screenshot. Which explains why yours perfectly matches tshering's ^^. And doesn't really help us .

TL;DR: My bad, I should really have mentioned from the start that I was thinking of something taken from nickel ;/. Brainfart >_<'.

FWIW, KOReader currently uses something like
Code:
ksmGeometryValuesN=758x1012+0+0
ksmGeometryValuesS=758x1012+0+12
ksmGeometryValuesE=1012x758+0+0
ksmGeometryValuesW=1012x758+12+0
(If my math/logic is correct, which, given my track record tonight, is debatable ^^).

But since I'm not quite sure 12px is actually the proper amount of hidden pixels, take that with a grain of salt. One potential other value would be 10 instead, so:

Code:
ksmGeometryValuesN=758x1014+0+0
ksmGeometryValuesS=758x1014+0+10
ksmGeometryValuesE=1014x758+0+0
ksmGeometryValuesW=1014x758+10+0

Last edited by NiLuJe; 02-20-2015 at 05:58 PM. Reason: Potentially fixed my geometry examples. Or broke them further. :D.
NiLuJe is offline   Reply With Quote