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
Current RGB API does not play well with others (animation from config file overwrites any other use of the pixels).
The improved API should aim to do the following:
Safely avoid touching hardware when pixel subsystem is not initialized or otherwise disabled
Allow "reserving" bitmask of individual pixels (w/ uint32_t owner tag or similar for debugging)
Allow "releasing" bitmask of reserved pixels (w/ uint32_t owner tag or similar for debugging)
Automatically pause any configured animation when at least one pixel is reserved
Automatically resume configured animation when last reserved pixel is released
Note: The above functionality is a pre-requisite to improving debug output. In particular, want to have assert() and hard_assert() handlers cause specific unique animation to make it clear there is a code issue (vs. hardware lockup), even with no debugger attached.
The text was updated successfully, but these errors were encountered:
Current RGB API does not play well with others (animation from config file overwrites any other use of the pixels).
The improved API should aim to do the following:
uint32_t
owner tag or similar for debugging)uint32_t
owner tag or similar for debugging)Note: The above functionality is a pre-requisite to improving debug output. In particular, want to have
assert()
andhard_assert()
handlers cause specific unique animation to make it clear there is a code issue (vs. hardware lockup), even with no debugger attached.The text was updated successfully, but these errors were encountered: