Looking closely into v3, the biggest things that may change the way users use AdvantageKit are the following:
- Subsystems have been renamed to Mechanisms
- Mechanisms have no periodic methods by default
The simplest way I can see is using addPeriodic on the scheduler, which sideloads a command onto the Scheduler that is ran at the normal loop rate with no requirements. Or if periodic logic would be avoided like they are hoping to lean users towards with v3, calling something that checks if the timestamp has changed, and updating as necessary.
What are your thoughts about the recommended way to utilize the new framework? And do you have any plans for supporting one or both in templates?
Thanks.
Looking closely into v3, the biggest things that may change the way users use AdvantageKit are the following:
The simplest way I can see is using addPeriodic on the scheduler, which sideloads a command onto the Scheduler that is ran at the normal loop rate with no requirements. Or if periodic logic would be avoided like they are hoping to lean users towards with v3, calling something that checks if the timestamp has changed, and updating as necessary.
What are your thoughts about the recommended way to utilize the new framework? And do you have any plans for supporting one or both in templates?
Thanks.