Skip to content

♻️ Motion encapsulation #27866

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: bugfix-2.1.x
Choose a base branch
from

Conversation

thinkyhead
Copy link
Member

@thinkyhead thinkyhead commented May 19, 2025

Without changing too many semantics this PR aims to encapsulate all the motion data and code in a Motion singleton class, making it more obvious in the rest of the codebase which calls are being made to Marlin motion code versus similarly-named methods in other APIs.

This is a work-in-progress along with a number of other refactors posted for CI testing. This PR will be followed up with encapsulation of MarlinCore.* code in a "marlin" singleton object.

@thinkyhead thinkyhead force-pushed the bf2_motion_encapsulation_PR branch 13 times, most recently from 90658b7 to 225ceea Compare May 19, 2025 07:29
@thinkyhead thinkyhead force-pushed the bf2_motion_encapsulation_PR branch 15 times, most recently from 6adbacb to 2774073 Compare May 19, 2025 20:54
@thinkyhead thinkyhead force-pushed the bf2_motion_encapsulation_PR branch 8 times, most recently from 772d46e to 9344ccd Compare May 19, 2025 23:03
@thinkyhead thinkyhead force-pushed the bf2_motion_encapsulation_PR branch from 9344ccd to 95c1e6d Compare May 19, 2025 23:08
@thinkyhead thinkyhead force-pushed the bf2_motion_encapsulation_PR branch from 95c1e6d to f4c6867 Compare May 19, 2025 23:12
@thinkyhead thinkyhead added this to the After 2.1.3 milestone May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant