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

Force Move Missing #1880

Closed
FoldZero opened this issue May 12, 2024 · 3 comments
Closed

Force Move Missing #1880

FoldZero opened this issue May 12, 2024 · 3 comments
Labels
💡 Type: FR Requests a new feature

Comments

@FoldZero
Copy link

Requested feature:

image
I have to switch back and forth between Mainsail and Fluid as i need this feature when fixing print crashes.
I would prefer to stay on Mainsail.

The feature should unlock the motors and allow the directional control full movement, caveat emptor

Solves the following problem:

I have to switch back and forth between Mainsail and Fluid as i need this feature when fixing print crashes.
I would prefer to stay on Mainsail.

Additional information:

No response

@FoldZero FoldZero added the 💡 Type: FR Requests a new feature label May 12, 2024
@meteyou
Copy link
Member

meteyou commented May 12, 2024

we decided not to implement it, because you can easily destroy your whole printer with it. if you need it, you are welcome to use a macro for it.

@meteyou meteyou closed this as not planned Won't fix, can't repro, duplicate, stale May 12, 2024
@FoldZero
Copy link
Author

caveat emptor.
i strongly disagree with baby sitting, for such a useful feature in the hands of the experienced.
A settings checkbox and a warning?
I can but ask. :D

@meteyou
Copy link
Member

meteyou commented Sep 24, 2024

caveat emptor. i strongly disagree with baby sitting, for such a useful feature in the hands of the experienced. A settings checkbox and a warning? I can but ask. :D

We might implement it once we have worked through the entire backlog, but right now, we have more important features to implement. Maybe a contributor will do it. We are concentrating on essential functions that every user can use to simplify everyday life with Klipper.

I'm also an experienced Klipper user, but I don't know of any use cases in the last few years where I needed force_move. This feature is considered way too important and very often misused. For this reason, it's hazardous for users who think they are experienced but are still learning.
Just my 2 cents

TL ;DR
If you think this feature is essential for you, feel free to fork Mainsail and if you implement a good solution to protect new users, feel free to create a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 Type: FR Requests a new feature
Projects
None yet
Development

No branches or pull requests

2 participants