-
-
Notifications
You must be signed in to change notification settings - Fork 443
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
Ability to choose option at print startup #1337
Comments
Hi, thats what i am looking for.
Then, in START_PRINT, I call SHOW_OPTION_BED_MESH. The window appears with configured buttons, but after ckicking one option nothing happens -and during the window appears, theSTART_PRINT macro continues to be processed What else do I have to do? |
I would say that you now need 2 changes:
Note: I have not tested this, but in theory, it should work... |
Thanks for the answer. One more question: how to get the window closed after clicking an option? |
Use |
also found out in the meantime. |
Given the above, I think we got a good compromise for this feature by using the macro prompt dialogs! As such, I am now closing this ticket. |
One more thing: If i want to pause a makro (pause the gcode from processing), i cannot use PAUSE because thie is the macro pause.... |
There is a limit to what is possible with the current Klipper provided support... Anything more than the described above, I think we will need upstream support added directly in Klipper. |
Is your feature request related to a problem? Please describe
Is there a way to program fluidd to query before starting a print? In Start_macro I have the options to run a completely new Bed_Mesh or load a specific profile or just create a Bed_mesh within the boundaries of the part to be printed. Currently I'm commenting out the options that are not wanted at startup. It would be nicer if a window would open when I started printing where I could select the option
Describe the solution you'd like
nothing
Describe alternatives you've considered
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: