Quote:
Originally Posted by NiLuJe
@desterly: Hard to tell what's a page turn and what isn't, given that everything happens in the space of 10s ;o).
Anyway, I was inclined to say that it's probably just an eInk quirk, and your EDIT about rotation being involved only furthers that impression  .
I'll see if I can reproduce anything locally when I'm testing the Elipsa support later this week . |
Yep, definitely an eInk quirk. (It's the visible effect of a race between our blit, nickel's refresh, our refresh, and the driver trying to merge those two together).
It's more visible on Inverted rotations (or not, depending on positioning) purely because of where in the buffer region our blit hits.
TL;DR: Nothing we can do about it (... besides making it worse all the time by bringing back a delay
).