Skip to content
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

Validate fixture addressing #10

Open
craftyjon opened this issue Apr 7, 2013 · 2 comments
Open

Validate fixture addressing #10

craftyjon opened this issue Apr 7, 2013 · 2 comments

Comments

@craftyjon
Copy link
Contributor

Life is a lot easier if we can validate the addresses. Most importantly, fixtures on a strand need to have continuous addressing from 0 to N. Strands themselves don't necessarily need to have continuous addressing, since each strand is handled by its own controller. We can save on network overhead if a bulk strand write can leave out the fixture addresses by assuming that they cover a continuous range.

@zbenjamin
Copy link
Contributor

We now validate that fixtures have unique addresses, but not that they're consecutive. The default is to create consecutive addresses, though, so it's easier for the user to get it right.

@craftyjon
Copy link
Contributor Author

TBD: This issue might be moot with the move to PixelGroups and offset-based addressing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants