@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

).