New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pixel buffer accepts tuples but returns lists with different value #71
Comments
Not sure why the list/tuple change. But change in value is from https://github.com/adafruit/Adafruit_CircuitPython_NeoPixel/blob/master/neopixel.py#L232 which multiplies by brightness. |
Can you post full code so we can also see how you initialized the NeoPixel object. |
What version of the library are you using? |
@caternuson, the code is in a public repo. You can see where I define colors as tuples And where I basically want to say "if the pixel is not already set to X, set it to Y". That call returns the color as a list. @tannewt 4.1.0
You can see I've worked around the tuple/list issue by converting the response from neopixel.
|
I think you might be hitting this: |
This issue is resolved.
|
On version 4.1.0
color values passed as tuples
(r,g,b)
are returned as `[brightnessr,brightnessb,brightness*c]Prints
[40,0,0]
The text was updated successfully, but these errors were encountered: