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
Is there an existing issue for this feature request?
I have searched the existing issues
Is your feature request related to a problem?
As an extension of #2191, while I can roughly estimate the time that pauses will occur this is a somewhat manual process and needs to be re-calculated for each subsequent pause from when I resume the print.
Which printers will be beneficial to this feature?
All
Describe the solution you'd like
The "Printing Progress" section of the "Device" tab currently shows the current layer, the remaining time, and the local time of completion. On prints with planned pauses, an additional field showing remaining time till next pause, local time of next pause and optionally the layer of the planned pause would clearly communicate the next time user interaction is required.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this feature request?
Is your feature request related to a problem?
As an extension of #2191, while I can roughly estimate the time that pauses will occur this is a somewhat manual process and needs to be re-calculated for each subsequent pause from when I resume the print.
Which printers will be beneficial to this feature?
All
Describe the solution you'd like
The "Printing Progress" section of the "Device" tab currently shows the current layer, the remaining time, and the local time of completion. On prints with planned pauses, an additional field showing remaining time till next pause, local time of next pause and optionally the layer of the planned pause would clearly communicate the next time user interaction is required.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: