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

Add print interruption warning to auto update dialog #2152

Merged
merged 1 commit into from Oct 13, 2017
Merged

Add print interruption warning to auto update dialog #2152

merged 1 commit into from Oct 13, 2017

Conversation

ntoff
Copy link
Contributor

@ntoff ntoff commented Oct 13, 2017

What does this PR do and why is it necessary?

Adds a warning to the auto updater dialog about possibly resetting your printer. This typically only applies when using octoprint to monitor a printer that is printing off an SD card, which was initiated via the LCD panel in which case OctoPrint has no way of knowing the printer is busy and therefore won't automatically block the installation of updates.

How was it tested? How can it be tested by the reviewer?

Install an old version of a plugin or octoprint, allow it to notify you of an update, observe the new dialog box warns about a possible reset

Any background context you want to provide?

Fills in a missing piece of a feature request that was missed on the first PR

What are the relevant tickets if any?

#2131

Screenshots (if appropriate)

image

Further notes

@foosel foosel merged commit 020180a into OctoPrint:maintenance Oct 13, 2017
@foosel
Copy link
Member

foosel commented Oct 13, 2017

Yay! 👍

@ntoff
Copy link
Contributor Author

ntoff commented Oct 16, 2017

note/question

Should the h5 be changed to a bold? or just removed entirely?

It's been driving me insane ever since the discussion. I thought about the big scary warning being the next "section", first section being release notes, but since the first "section" doesn't have a bold heading, should I just remove the bold/heading all together and make it normal text? Or do you want to just take care of it on your end and I should stop obsessing over it?

@foosel
Copy link
Member

foosel commented Oct 17, 2017

I'll take care of it, no need to obsess ;)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants