View Single Post
Old 08-05-2016, 03:23 PM   #5
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by zxczxc View Post
Thanks, straight to the point!
Although I think this only gives 270, so we can use 0, 90, 270, but still not 180...? A shame if true.
The "inversion of framebuffer wangle" twobob mentions could work (using a variant of the screen rotation extension for damaged eink screen). In that case, rotating the touchscreen may be desirabe as well. I would need some tweaking to the C code and a recompile...
geekmaster is offline   Reply With Quote