View Single Post
Old 05-18-2014, 03:04 PM   #19
hawhill
Wizard
hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.
 
hawhill's Avatar
 
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
I think that bulsa will probably be correct in assuming that GTK does only "fast" refreshes, which leave a bit of ghosting on the display. I'm also about sure that the GTK modification will *also* du "full" refreshes, i.e. going through a black/white transition - it'll just look too bad if they didn't. I guess they implement it similarly than I did - use some kind of limit on screen space and number of fast refreshes to trigger a full refresh.

However, even if they *did* implement it in GTK, then I'm really asking myself what way they use. It would show on an strace for the process using GTK. Plus, it would be also subject to the race condition bulsa talked about before. Then, as I consider that condition mainly being theoretical, Amazon's engineers might have chosen to go for that compromise, too.
hawhill is offline   Reply With Quote