View Single Post
Old 11-29-2021, 09:45 PM   #114
Deobulakenyo
Guru
Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.
 
Posts: 706
Karma: 2153490
Join Date: Aug 2021
Location: Stupid Philippines
Device: Kobo Libra 2, Boyue Likebook P78
Quote:
Originally Posted by NiLuJe View Post
@Deobulakenyo: You failed to actually modify the relevant key=value entries in that snippet?

EDIT: Also, column/row are for the embedded bitmap fonts, you'll want to tweak truetype_w & truetype_y instead. For the top-right corner, an y value close to 0 and a small dip into the negatives on the x axis should do the trick (we can't give you a perfect answer, because that's not a monospaced font, so it's all pixels, and it'll vary depending on what's actually displayed and at which size).
Thank you very much. Now i understand. I was able to fix it using the following settings. I aligned the nanoclock with my header in the Y axis and with the edge of the book cover in the X axis using these configs:

Code:
truetype_size=6.0
truetype_px=0
;; ^NOTE: size is in pt, px is in pixels. If set to non-zero, px takes precedence.
;;        In case you ever need to do the maths yourself, px = dpi / 72.0 * pt
truetype_x=-220
truetype_y=22
Deobulakenyo is offline   Reply With Quote