RogueMaster
RogueMaster
> Or just don't do anything, but the screen will end up blank for a second. I've been using current code for Clock since I started it back in April...
> You should be writing robust code, not just code that works now. I'm satisfied with the code working as desired, it not working in some future case means it...
> * Suggest calculating timer from datetime instead of a counter to minimize drift Now this is done 😄 Thank you!
> As a matter of fact, your timer variables are not guarded and should be put into `ClockState` instead. Agreed, thank you, updated.
If the person stops the timer, I need to still calculate the seconds that were timed before the Stop, they can Start again without a Reset, so timerSecs is needed.
> Here's a thought: why do you need current datetime in the state at all? Just get current whenever you need it. True, done. Think you could help me find...
Why close?
It will let you create different branches within your fork if you want to make a dev branch to PR this again, DM me on Discord if you need help.
The benefits of backing up and restoring from SD are obvious. Is this something that is wanted on the main FW? Due to changes in the code, and the fact...
Since the moderators of this community don't enforce GPL restrictions on other members and moderators changing the licensing of an open source submission, I am withdrawing my Pull Request. GPL...