-
Notifications
You must be signed in to change notification settings - Fork 10
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
[REQUEST] be able to select any neopixels in the series for a static colour #18
Comments
This isn't a pull request, not sure what the wording's for. To allow any Pixels to be set as static or not wouldn't be practical, as it overcomplicates the way LED updates works. The most that could be reasonably offered is a toggle determining whether static pixels are set from the first or the last X pixels of the strand; this requires work in the firmware to support the option first. |
Adding depends on TeamOpenFIRE/OpenFIRE-Firmware#26 |
I could work with that. Also could you allow more than just 3 static configuration? |
This issue is not for piling on other problems unrelated to the title of the issue you're posting in; all unique issues need separate posts please. Regardless, adding more than three static emitters are not likely, because four pixels is close to if not the practical limit of how many emitters you can have running off USB power anyways. |
(Request) here is more granular control and static colour assignment of any neopixels wired.
(Background)
Currently you can only select first 3 neopixels for static colour configuration, leaving the rest to be configurable my things like Qmamehooker.
In addition to the issue, we are limited by the exact sequence of the first 3 neoixels, e.g. I can't configure only the third for a static colour.
Sometimes for wiring purposes, it's cleaner to have the first neopixel placed where you want mamehooker to control and subsequent pixels, to be static.
The text was updated successfully, but these errors were encountered: