Skip to content

Conversation

@gigapod
Copy link
Member

@gigapod gigapod commented Feb 15, 2025

Move the one class to two, with each focused on the one of the applications the board can run.

Since the board only can run one app at a time, it made no sense to have one class with everything jammed into it. The result was large and annoying to manage.

…es with a core base. The two main classes now correspond to the application running on the XM125 - v1 of this library had one class that contained everything - nuts. This will break backward compatablity, but the end user just needs to change the name of the class they are using
@gigapod gigapod merged commit 66d41da into develop Feb 15, 2025
@gigapod gigapod deleted the feature/class-refactor branch February 15, 2025 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants