View Single Post
Old 10-26-2022, 01:45 PM   #109
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by sherman View Post
Thanks everyone for the investigations!

My development was indeed on a recent firmware, Going back to older firmware versions
is a PITA, so I don't do it very often.

As to what I'm doing QSS wise, NickelClock Copies the embedded ReadingFooter.qss, removes the stuff before the font settings, changes #caption to my own ID, and applies the new stylesheet. I obviously need to devise a more robust solution...
I think every single line of ReadingFooter.qss is patched by one or other of 2 existing patches.
  1. Reduce new header/footer height patches ReadingFooter min-height and max-height
  2. Custom header/footer captions patches #caption font-size and (optional) #caption font-family. Also ReadingFooter qproperty-footerMargin
I use both of those patches myself, but NickelClock seems to be working OK for me on Libra2, ClaraHD, AuraOne and Forma. This sounds like a minor miracle based on what you said about how NickelClock works.
jackie_w is offline   Reply With Quote