add timer.starta and timer.stopa to stop and start a systimer that calls a bitlash function #235
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Im actually not using built in reports because I dont need all that data or all those cycles
Im collapsing what I need into a command.report instead, but theres no way to schedule things from bitlash, so I made this and I think it might be handy.
timer.starta(10000,"power.report",1);
timer.stopa
went with letters instead of numbers to not confuse with timer0, timer1 etc on arduino
I actually kind of like this for the events system too. Then if you events.stop you actually get those 3 timers back too.