Native FBInk: Another small tool to print crap on your screen!

[PoP]

...let's paint filled rectangles freely. Yay!

-katchy, à la Mondrian:


or with more ~faithful outlines:


[EDIT 2020-02-03 fix RANDOM in v0.20]
[EDIT 2020-02-04 add Outline variant]

[NiLuJe]

Released v1.22.0!

A few fixes here and there, a few minor performance improvements in both font rendering codepaths, and a few new API calls geared at making life easier for grid-layout aficionados .

[NiLuJe]

Released v1.22.1!

Minor tweaks to fbdepth to better handle legacy einkfb Kindles (i.e., < K5), as well as the nightmode flag discussed in the last few pages of this thread .

[PoP]

Sweet

I see the new COZETTE fixed font.

But how can I optionally request the 8x16 UNIFONT and its double width UNIFONTDW from the command line? API only at this time?

So far I am using its counterintuitive True Type build.

As Churchill said about Martinis, one font is good, two is too many and three is not enough.

[NiLuJe]

Not really, it requires a custom build with UNIFONT set, because the binary size blows up ridiculously when it's compiled in ;p.

That said, you're probably better off with the Vector variant .

(This was more of a "let's see how this could work" experiment than anything. You can get pretty sharp results with the Vector variant if you request perfect multiples of the expected pixel size in pixels instead of points. The performance hit is not too bad, either).

[miran]

currently using fbink it displays text for a second and disappears in kterm
though when keeping text aimed at keyboard(using -y) it stays till keyboard is pressed
is there any way to keep text there forever,
like:- when i run the command background goes white text stays on forever.
I press power button > back to homescreen

[NiLuJe]

@miran: *Insert Tennant's 10th doctor "What?!" gif here*.

Seriously, try again with proper sentences, punctuation, and actual code examples, because I have no idea what you're trying to do and what's actually happening.

From what little I understood about what you said, you're running fbink commands from *within* kterm?
In which case, that's not going to work. It's a terminal. Its job is to update the screen. Meaning it'll race w/ fbink, and depending on where you print and/or what fbink itself requires the terminal to print, shit will happen.

[miran]

Thanks for replying, sorry for bad typing

Actually i am trying to print text using fbink in kterm but it get cleared by kterms own display after a millisecond.
I tried kual launch of a sh file with same command in it but if i click somewhere it gets cleared again.
I wanted to know if there is anyway to keep text on screen without it getting cleared. Something like this:-
1. it clears screen white
->2.displays text
->3.when i press power button, goes back to homecreen.
(+ is there any way to get current screensaver state like is it on or off in kterm)

[NiLuJe]

Well, no, not unless you control *everything* that's drawing on screen, which you don't.

[miran]

ok i looked at code of kindle menu it has this line
lipc-set-prop com.lab126.pillow customDialog '{"name": "blank"}'
with comment draw blank screen

[yparitcher]

@miran
the easiest way to do this is to fake a press of the power button with lipc, wait until the screensaver is drawn, and then draw what you want on top. this will then stay until the power button is pressed. (in other words make your own screensaver)

[miran]

@yparitcher
thanks that is a good idea
can u tell how to wait till ssaver is on
and if my text is dynamic(change every hour or so) will command/script still be executing after ssaver

[yparitcher]

for a similar project you can look at my https://github.com/yparitcher/kindle-zmanim
it uses fbink to display a dynamic screensaver.
It is currently written in C, but if you look at the earlier commits most of it used to be in shell if that is easier for you

for my details see my other posts on this topic https://www.mobileread.com/forums/sh...8&postcount=27

[miran]

thanks a lot will surely check

[NiLuJe]

Released v1.22.2!

Some minor updates and fixes.