Currently, the getchar() function manually polls the keypad to determine which key is being pressed, and some--but not all--apps will debounce this reading to avoid duplicate presses. Unfortunately, while rendering the screen at four frames per second looks fine, sampling the keypad only four times per second is a bit annoying.
Close this issue when we use GPIO interrupts to trigger button sampling, so that we can sample away from frame rendering.
Currently, the
getchar()function manually polls the keypad to determine which key is being pressed, and some--but not all--apps will debounce this reading to avoid duplicate presses. Unfortunately, while rendering the screen at four frames per second looks fine, sampling the keypad only four times per second is a bit annoying.Close this issue when we use GPIO interrupts to trigger button sampling, so that we can sample away from frame rendering.