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.

Sign up for GitHub

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

Jump to bottom

Octoprint error message not closable #12325

Closed
2 tasks done
kylane opened this issue May 23, 2022 · 7 comments
Closed
2 tasks done

Octoprint error message not closable #12325

kylane opened this issue May 23, 2022 · 7 comments
Labels
Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Type: Bug The code does not produce the intended behavior.

Comments

@kylane
Copy link

kylane commented May 23, 2022

Application Version

5.0.0-beta1

Platform

Win11

Printer

Ender 3

Reproduction steps

Opening Cura without turning on my octoprint first shows an error on load that I cant close until I start octoprint.

image

Actual results

Cura error opens offscreen making it impossible to dismiss.

Expected results

Popover panel should still be closable - perhaps scroll the contents within?

Checklist of files to include

  • Log file
  • Project file

Additional information & file uploads

NO need - easily reproducable.
@kylane kylane added the Type: Bug The code does not produce the intended behavior. label May 23, 2022
@fieldOfView
Copy link
Collaborator

Issues with the OctoPrint Connection plugin should go here:
https://github.com/fieldofview/Cura-OctoPrintPlugin/issues

One could argue that Cura should handle messages that are too long in a better way.

@fieldOfView
Copy link
Collaborator

Note that you are using a beta version of Cura 5, and the full release has been out for a while now. Please update.

@fieldOfView
Copy link
Collaborator

(and finally)

NO need - easily reproducable.

No, we definitely need logs. It may be easily reproducible for you, but it may be less easily reproducible for us. If you would like to see this fixed in a timely fashion, please help us.

@nallath
Copy link
Member

nallath commented May 23, 2022

One could argue that Cura should handle messages that are too long in a better way.

I figured that was also what this bug was about.

@Vandresc Vandresc added the Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. label Jun 7, 2022
@MariMakes
Copy link
Contributor

Quick update,
We discussed it with the team and see value in making long messages scrollable so they can be closed, but we totally forgot to update this issue.

For internal reference CURA-9374

Thanks for the report! 👍

@MariMakes MariMakes added Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. and removed Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. labels May 15, 2023
@MariMakes
Copy link
Contributor

Hey @kylane,

Quick update from our side 👋

Our new developer @wawanbreton was able to resolve your issue here: #16509
Long messages now have a scroll bar. image

I'll be closing this issue and you will see the fix in the upcoming release.

@kylane
Copy link
Author

kylane commented Oct 17, 2023

Hey @kylane,

Quick update from our side 👋

Our new developer @wawanbreton was able to resolve your issue here: #16509 Long messages now have a scroll bar. image

I'll be closing this issue and you will see the fix in the upcoming release.

Awesome work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@fieldOfView @nallath @kylane @MariMakes @Vandresc