IDK if anyone else wants to take a stab at this, the files are a bit complicated. I probably won't for at least a few weeks, probably longer as I don't currently have a use-case.
Some improvements:
[x] queue overflow management (Currently will overflow without warning)
[x] settable maximum queue length (currently "const"d at 50 pin state changes)
[ ] Documentation for how the internal systems work, so that future students can update it
[x] Indefinite irregular pattern handling
The idea for the last one is that you might have one long blink followed by three short blinks, or maybe Morse code or something. Currently, doing this pattern once is feasible, just call aonoff twice with the two different durations and they will be queued one after the other. The problem is if you want to indefinitely repeat a non-uniform blink pattern. The internal queuing system currently only supports a single pattern indefinitely.
IDK if anyone else wants to take a stab at this, the files are a bit complicated. I probably won't for at least a few weeks, probably longer as I don't currently have a use-case.
Some improvements:
The idea for the last one is that you might have one long blink followed by three short blinks, or maybe Morse code or something. Currently, doing this pattern once is feasible, just call aonoff twice with the two different durations and they will be queued one after the other. The problem is if you want to indefinitely repeat a non-uniform blink pattern. The internal queuing system currently only supports a single pattern indefinitely.
What would a call to this method look like?
Maybe
? Seems clunky but I don't currently have a better idea. Maybe you could do something like
Where you could queue up indefinite patterns between those two guards.
Any suggestions?