This is an experimental version.
miniclock.cfg changes:
Code:
#
# To debug, set to 1 (will print event parser)
#
debug=0
#
# whitelist of accepted events that should update miniclock
# ABS:MT_POSITION_X/Y: touchscreen coordinates
# KEY:F23/F24: forma forward backward buttons (to be confirmed)
# KEY:POWER: going into standby manually
#
whitelist=ABS:MT_POSITION_X ABS:MT_POSITION_Y KEY:F23 KEY:F24 KEY:POWER
#
# cooldown num time
#
# after receiving num unrecognized events in a row,
# stop listening to all input for <time> seconds.
# (helps avoid power consumption during standby)
#
cooldown=3 30
Set debug=1 in the config file and the events will be printed on screen. This is useful to determine new values for the whitelist. (I wasn't sure about Forma page button event as I don't have a Forma... the F23/F24 I found online somewhere, not necessarily correct. I also don't know if all touchscreens use the MT_POSITION_X event or not.).
If non-whitelisted events keep coming in, MiniClock will stop listening to the input devices for a time (cooldown). This is in hopes of avoiding drain when something keeps sending odd events. Not sure if this works.
Add "{debug}" to the date format string and cooldown itself will update the clock, so you see it happens at all. Otherwise {debug} will show which event caused the update.
Please let me know if it works for you...