View Single Post
Old 04-28-2016, 12:06 AM   #46
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
This will not work on the K1 as-is, because the "waitforkey" command keycode parameter is not optional on the K1. There are also no input event devices either, so AFAIK the only way to access key presses from a script is with "waitforkey". As mentioned in my K1 thread, I will need to modify the "waitforkey" call to fork off a process for each possible keycode, and save that specific keycode from whichever process fired, instead of waiting for a generic "any" key that the newer "kindles" support.

While at it, I will add support for all the kindles with keyboards (except I cannot test on a K2 which I do not have), including my K1.
geekmaster is offline   Reply With Quote