diff options
| author | Tom Hodson <thomas.c.hodson@gmail.com> | 2022-11-22 14:30:24 +0100 |
|---|---|---|
| committer | Tom Hodson <thomas.c.hodson@gmail.com> | 2022-11-22 14:30:24 +0100 |
| commit | 0b3a1ed24402bee9b2e5c242ea79cb51cfafd4a0 (patch) | |
| tree | e3637e55a916cb3a569f301fc620794570a02c23 /rules.mk | |
| parent | 2455a922c6c62dcb94106cef7214cf3f28c3ce55 (diff) | |
| download | Sensor-Watch-0b3a1ed24402bee9b2e5c242ea79cb51cfafd4a0.tar.gz Sensor-Watch-0b3a1ed24402bee9b2e5c242ea79cb51cfafd4a0.tar.bz2 Sensor-Watch-0b3a1ed24402bee9b2e5c242ea79cb51cfafd4a0.zip | |
WIP: Add support for bicolor led in the simulator
I noticed that the bicolor led isn't supported in the simulator. Here is a quick mockup of how I would add support for it.
I added an SVG filter to the #light rectangle in the SVG which lets us multiply the colours by a matrix in code. I then insert values so that the original green colour gets mixed into the combination of red and green requested by `watch_set_led_color`
# Testing
So far I've only tested this with the standard firmware build but it seems to work.
# Possible issues
I wasn't 100% sure what to do when red + green > 255, current behaviour is that it gets clamped to 255 in the simulator.
Diffstat (limited to 'rules.mk')
0 files changed, 0 insertions, 0 deletions