You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The serial write of lightsarray in processing ins't working as expected ... 'show all leds' on and off is working ... but when I try and do an auto mapping more than one led lights up simultaneously (up to 3 of them) during the mapping process ... usually one of them is colored red ... also with the 'showLedUnderMouse' more than one led lights up ... and nowhere near the mouse ... I have tested the arduino side of things and it seams to be coming from the byte serial write out of processing ... is this a versioning issue maybe? what version's were used for development? Is this possibly a signed unsigned issue perhaps in doSingleLED()? Is it even necessary to send the whole led array (lightsarray) over serial each draw frame to do this? couldn't it just be a simple protocol to step through the leds one by one?
arduino-1.8.6-windows
PROCESSING 3.4 (REV 0265) - 26 July 2018
The text was updated successfully, but these errors were encountered:
The serial write of lightsarray in processing ins't working as expected ... 'show all leds' on and off is working ... but when I try and do an auto mapping more than one led lights up simultaneously (up to 3 of them) during the mapping process ... usually one of them is colored red ... also with the 'showLedUnderMouse' more than one led lights up ... and nowhere near the mouse ... I have tested the arduino side of things and it seams to be coming from the byte serial write out of processing ... is this a versioning issue maybe? what version's were used for development? Is this possibly a signed unsigned issue perhaps in doSingleLED()? Is it even necessary to send the whole led array (lightsarray) over serial each draw frame to do this? couldn't it just be a simple protocol to step through the leds one by one?
arduino-1.8.6-windows
PROCESSING 3.4 (REV 0265) - 26 July 2018
The text was updated successfully, but these errors were encountered: