summaryrefslogtreecommitdiffstats
path: root/quantum/quantum_keycodes.h
diff options
context:
space:
mode:
authorTerryMathews <terry@terrymathews.net>2018-08-26 19:12:41 +0200
committerJack Humbert <jack.humb@gmail.com>2018-08-30 03:03:23 +0200
commitd12d058baeb1f26a05077f88406bc3222f185129 (patch)
treeb41930947ca634ee84ab01f09ec64fb125fd437c /quantum/quantum_keycodes.h
parent972388447b03e1c403f20acd6c6b04363864f66e (diff)
downloadqmk_firmware-d12d058baeb1f26a05077f88406bc3222f185129.tar.gz
qmk_firmware-d12d058baeb1f26a05077f88406bc3222f185129.tar.xz
Autodetect lack of screen presence
This is the simplest, most efficient way I could come up with to silence the "Failed to start write 60" error that occurs when QMK tries to talk to a screen that doesn't exist. iota_gfx_init passes a success boolean. We catch that into a global bool (we could rewrite multiple functions to pass this as an argument, but given the number of keyboards using this code it seemed less disruptive this way) and then use that as a conditional on running the iota_gfx_task in matrix_scan_user. Tl;dr: if the screen doesn't init, the screen write code doesn't run.
Diffstat (limited to 'quantum/quantum_keycodes.h')
0 files changed, 0 insertions, 0 deletions