-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Feature Request: Insert Pause and/or custom Gcode between layers in 3D preview #3092
Comments
I think this would be better on a per object basis. If you print multiple objects one at a time then you might not want to pause at the same layer for every object, only for the one where you want to insert something. This could still use your interface idea (which I like) but also have an object selection. |
@mrvn |
@mrvn |
This would be a nice feature for inserting captive nuts like in this thing:
|
Someone's welcome to try to work out the UI code for it (and it is 90-95% UI code work), and I'll review a pull request. |
It would be nice if - at least - slic3r allowed to you find particular moment and locate the G-code line for it. |
3092-pause.zip Attached is the diff as I don't have access to create a branch ... but it's been a while since I worked with git. If there's a way to get this into a PR, let me know. This is not exactly as described, but it's close. By adding "pause heights" to the shortcuts it will be accessible from the layers screen. |
@goofdad To create a Pull Request:
|
Done. |
Any progress on this? It's been a few years and this would be really handy. |
Can we just get an interface exactly like the cut interface? Just change the name to pause? |
Often it is useful to pause the print to change filaments, or to insert components into the print. While this can be done by many different methods, such as manually editing the Gcode, or using a script, it would be nice to have a simple way to do this in Slic3r.
I propose adding a "insert pause script between layers" button to the 3D and 2D preview windows.
Functionality would be:
First mentioned in issue #1055.
Better implementation possible if implemented with or after #2979
The text was updated successfully, but these errors were encountered: