Skip to content
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

Add Ender-3 Pro without clip boundaries for magnetic bed #7466

Merged
merged 1 commit into from Apr 14, 2020

Conversation

kazooless
Copy link
Contributor

In this discussion: #7252

Some were pointing out the Ender-3 Pro comes with a magnetic bed without clips making the entire surface of the bed printable. The disallowed areas in the standard Ender-3 are not easily removed. @Ghostkeeper seemed to indicate a new "Pro" profile is an acceptable solution. So, here it is.

P.S. I'm still very new to GitHub. I made this change in the 4.6 branch instead of master this time. Is this correct? (preferred by you?)

@Ghostkeeper
Copy link
Collaborator

Ghostkeeper commented Apr 14, 2020

P.S. I'm still very new to GitHub. I made this change in the 4.6 branch instead of master this time. Is this correct? (preferred by you?)

For Github this is fine. You can aim a PR to be merged into any branch. However for the Cura team's workflow it's incorrect. Before we start the public beta we always have a feature freeze. That means that only bugfixes are allowed in 4.6 at the moment. That's necessary to get the release stable. I hope you understand.

I'll change the base of this PR to master. That way it can get merged into 4.7 instead (which we will branch off in about 2 months).

@Ghostkeeper Ghostkeeper changed the base branch from 4.6 to master April 14, 2020 12:09
@Ghostkeeper
Copy link
Collaborator

Seems to work fine. No more clip collision areas. Thanks!

@Ghostkeeper Ghostkeeper merged commit ec31d7a into Ultimaker:master Apr 14, 2020
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.

None yet

2 participants