Quote:
Originally Posted by olup
Like, is there in the CLI a way to pipe some raw data to display on an area without relying to an image on the file-system ?
|
Nope, that's API only.
Quote:
Originally Posted by olup
And more obscurely, I understand your lib will not provide means to manage rotation. Is tehre documented ways to have those kind of kobos interpret the frame-buffer at 90° ?
|
Not really, but there's probably a saner method of doing what you're attempting to? (as in, actually rotate the framebuffer w/ fbdepth or something, depending on *why*, exactly, you think you need do to that?)
Quote:
Originally Posted by olup
Oh, also I wondered how I could pass on multiple string at once to fbink. I maintain a shadow matrix of letter to update only the changed one. But when big parts of the screen changes, I call fbink for each character on screen, and all those calls sent at the same time are prone to do weird stuff. Should I revise my logic or is there a way ? With demonized call maybe ?
|
You can pass multiple strings, but it will result in multiple refreshes, so you're more or less only saving a `fork`.
You could do something saner via the API, a temporary no_refresh switch for the batch of draw calls and fbink_grid_refresh and/or fbink_refresh on the final dirty region (àla InkVT).
TL;DR: The CLI is not really geared towards this sort of the stuff, but the API is
.