Thread: Clara HD Display time when reading
View Single Post
Old 07-29-2019, 10:01 AM   #263
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by frostschutz View Post
another day, another update. it should be more resilient to freezes and no longer miss inputs then

the touchscreen=1, button=1 that stopped working in the last few experimental updates, now merged into a generic input_devices settings:

Code:
#
# which /dev/input/eventX number devices to listen to
#
# input_devices=1    - event1 = touchscreen
# input_devices=0    - event0 = keyboard/buttons/magnet
# input_devices=1 0  - event1 event0 = both of the above
#
input_devices=1 0
If you have any issues with it please don't report them to me because I don't want to update it anymore

j/k, let me know if it works
Buttons no longer working at all, even after a reboot. Touch seems to be OK.

I must admit I'm totally confused because you say that button=1 is no longer required (and has been removed from miniclock.example.cfg) but there is still a reference to it in miniclock.sh (line 180). Does this mean that the built-in patch to libnickel is no longer required either?
jackie_w is offline   Reply With Quote