For a VT port I'm including FBInk exclusively to call screen refresh. A few questions:
- Are some refresh calls significantly more power-hungry than others? Right now I'm updating the screen by putting a flag up. Another thread loops "sleep, then if the flag is up do a FBink full screen refresh." Settings struct is full of zeros. I'm worried this is expensive.
- Are there examples of including this library in a project? My current approach includes a whole standalone copy of FBink in the program's local environment.
- Maybe not the place but not sure where else to ask... is there a common packaging example to adapt from? The VT needs a wrapper to manage exit + keep the stock UI from sleeping, overwriting the framebuffer, etc.
Thanks!