Advanced WS2812/SK6812 RGB/RGBW LED controller with on-the-fly Python animation programming, web code editor/control interface, 1D, 2D, and 3D display support, and E1.31 sACN support
Refinement on your (fast!) PR to my issue #19 this week. As I noted on the closed Issue:
prev_state and cycle count behavior are more accurately scoped to patterns, rather than the global execution.
The most flexibility for the user is when prev_state consistently holds the previous state, and t is reset at change of pattern/compile. If the user wants prev_state zeroed out at cycle 1, it's easy enough to do it. If not, it's irrelevant.
is there ever really a use case for preserving cycle count for the whole execution time?
This PR makes it only reset the cycle count, not the prev_state.
Refinement on your (fast!) PR to my issue #19 this week. As I noted on the closed Issue:
prev_state
and cycle count behavior are more accurately scoped to patterns, rather than the global execution.prev_state
consistently holds the previous state, andt
is reset at change of pattern/compile. If the user wants prev_state zeroed out at cycle 1, it's easy enough to do it. If not, it's irrelevant.This PR makes it only reset the cycle count, not the prev_state.