You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run a MMU as part of my configuration and at the end of each print I have a respond popup prompt to decide to unload or not unload the filament. If I am away from my printer I am not able to respond to the prompt with Mobileraker. Would be very useful to avoid leaving the heaters on for any length of time.
Proposed Solution
I would like to see the respond prompt I created displayed in Mobileraker as it does in Fluidd so that make the appropriate response.
Additional Context
[gcode_macro BUTTON_UNLOAD_FILAMENT]
gcode:
RESPOND TYPE=command MSG="action:prompt_begin Unload filament after print"
RESPOND TYPE=command MSG="action:prompt_text Do you want to unload the filament?"
RESPOND TYPE=command MSG="action:prompt_button_group_start"
RESPOND TYPE=command MSG="action:prompt_button Yes|YES_FILAMENT_UNLOAD|primary"
RESPOND TYPE=command MSG="action:prompt_button No|NO_FILAMENT_UNLOAD|secondary"
RESPOND TYPE=command MSG="action:prompt_button_group_end"
RESPOND TYPE=command MSG="action:prompt_show" ```
---
![Screenshot 2024-01-27 123609](https://github.com/Clon1998/mobileraker/assets/51010158/26b76180-250c-4872-b9d4-b85e9072461d)
Your input is valuable in shaping the development of our project. Thank you for taking the time to submit your feature request!
The text was updated successfully, but these errors were encountered:
Feature Request
Problem Description
I run a MMU as part of my configuration and at the end of each print I have a respond popup prompt to decide to unload or not unload the filament. If I am away from my printer I am not able to respond to the prompt with Mobileraker. Would be very useful to avoid leaving the heaters on for any length of time.
Proposed Solution
I would like to see the respond prompt I created displayed in Mobileraker as it does in Fluidd so that make the appropriate response.
Additional Context
The text was updated successfully, but these errors were encountered: