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

Printer information impairs touch responsiveness #2720

Closed
hzzm028 opened this issue Mar 2, 2022 · 7 comments · Fixed by #2722
Closed

Printer information impairs touch responsiveness #2720

hzzm028 opened this issue Mar 2, 2022 · 7 comments · Fixed by #2722
Assignees
Labels
bug Something isn't working
Milestone

Comments

@hzzm028
Copy link

hzzm028 commented Mar 2, 2022

A few days ago the GUI on my Pi Touchscreen offered me an Octodash update. I concurred.
Since the update I see every printer notification as an animated box, hiding the interesting information on my screen.
It's a permanent thing, like every other progress percentage pops up, heating progress etc. etc.
It never stops.

But that's not the main issue. Since this elegant box animation, the touchscreen responsiveness is down the drain.
Each action now takes around 3-5 seconds to react; be it simply navigation between menus or cancelling prints.

I've read through everything that ~/.config/octodash/config.json now offers, but I can't find anything that would let me disable the atrocious information box spam.

(Raspi 4B 8GB)

@hzzm028 hzzm028 added the bug Something isn't working label Mar 2, 2022
@Swap-File
Copy link

Swap-File commented Mar 2, 2022

Does a reboot temporarily fix your UI lag?

I've been noticing OctoDash UI lag that builds up over time. It seems related to the number of printer notification popups I get.

If I run a print with 800+ layers, I'll get 800+ printer notification popups in OctoDash. By the time the print is done, the OctoDash UI is almost un-usable. I get this many notifications because I have my slicer set to generate per layer notifications for my printer attached LCD12864 display.

If I just leave Octodash running with no prints going, the UI seems to stay responsive. Also, if I reboot, the UI lag goes away (until I run my next print, and get another few hundred notification popups).

@hzzm028
Copy link
Author

hzzm028 commented Mar 2, 2022

Does a reboot temporarily fix your UI lag?

Yes, today after a reboot it acted totally normal.
At the moment (after 3 hours of printing) it starts to feel somewhat slower.
Will report back this night after ~10-12 hours of printing.

I strongly feel such a significant change in UI behaviour should be optional.
There could be good reasons why someone wants the slicer notifications, while not having them clog up the dash.

@UnchartedBull
Copy link
Owner

Oh that is interesting, but can be possible. at the moment notifications aren't cleared (I didn't saw a reason since there were only a few usually). The next update will remove the info notifications from OctoDash again since they don't seem to be too useful.

I'm going to do some tests locally and see if I can identify the core issue.

@Swap-File
Copy link

Swap-File commented Mar 2, 2022

I don't mind the popup notifications (beyond the apparent lag), but it would be nice to adjust how long they stay on the screen and be able to set them up to self clear.

I do really like how this latest update enabled being able to display the camera while printing! Thanks for getting that working.

@jneilliii
Copy link
Contributor

Was that added as a core feature or is that part of my plugin? If it's in core features now I could remove that from the plugin.

@hzzm028
Copy link
Author

hzzm028 commented Mar 4, 2022

I see you (@UnchartedBull) trying to push an update, but on a factory octopi (Linux octopi 5.10.63-v7l+ #1496 SMP Wed Dec 1 15:58:56 GMT 2021 armv7l GNU/Linux) it doesn't run. Error in the attached picture.
Sorry I sounded a bit grumpy there to begin with.

The truth is, I take your tool for granted in my everyday recreational workflow, forgetting that there is a noble volunteer behind it, putting in all that effort to maintain it. Thank you.
20220304_174310
My quick assumption according to #2727 is, that i need to run the install script again.

@jneilliii
Copy link
Contributor

Running the manual update script should work and fix this bug at the same time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants