Quote:
Originally Posted by NiLuJe
@Mavireck: Fair enough  . Thanks for the feedback!
EDIT: I forgot to mention that print_raw_data *does* honor is_inverted (unlike restore) . The input data itself won't be touched, but what's written to the fb will be inverted.
(While with is_nightmode, the data is written as-is, and only inverted at refresh time by the EPDC, without affecting the fb).
EDITē: In some circumstances, you can also do a batch of prints with no_refresh enabled (so they don't actually trigger an eInk refresh, but are written to the fb), and finish the batch with a manual refresh call (thinking of printing a stack from bottom to top here, for instance ). |
I am always surprised by how many things are already integrated in FBInk... It should be used by more apps!
About is_inverted and is_nigthmode, is there one which is faster than the other?
As for the no_refresh, I forgot about it, so I did it completely differently :
my change
The advantage being that if one day I am to port this to another device or another library, it will be easier (because I use less-specific functions). I do at some point planned to separate what is general (the stack manager logic) from what is device-specific (FBInk functions, refreshs etc...).
That should make it easier if one day I want to port my apps to android for instance, or whatever device.