MobileRead Forums - View Single Post

NiLuJe · 09-28-2019, 12:16 PM

@davidfor: Thanks for the quick recap, I did not remember which method did what

.

----

Yeah, running fbink manually in a shell will save you *tons* of time

.

For the bottom corner enthusiasts, don't forget that you can pass *negative* values (to x & y; and top & left for opentype), which should help position stuff on bottom edges without having to know the screen resolution...

EDIT: I don't recall if this is exposed in miniclock, but FBInk now supports setting the opentype size in pixels, which makes what I detailed in my previous paragraph even more trivial, since everything is now in the same unit, so you won't have to figure (or compute) the point to pixel conversion yourself

.

(Although, you can: px = dpi/72 * pt).

09-28-2019, 12:16 PM	#303
NiLuJe BLAM! 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	@davidfor: Thanks for the quick recap, I did not remember which method did what . ---- Yeah, running fbink manually in a shell will save you tons of time . For the bottom corner enthusiasts, don't forget that you can pass negative values (to x & y; and top & left for opentype), which should help position stuff on bottom edges without having to know the screen resolution... EDIT: I don't recall if this is exposed in miniclock, but FBInk now supports setting the opentype size in pixels, which makes what I detailed in my previous paragraph even more trivial, since everything is now in the same unit, so you won't have to figure (or compute) the point to pixel conversion yourself . (Although, you can: px = dpi/72 * pt). Last edited by NiLuJe; 09-28-2019 at 05:46 PM.