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 have the beeper turned off in the printer settings so that it does not beep every time I touch the screen. However, after running prints that have been paused, the beeper will turn back on when I touch the screen. When I go into the settings, the beeper is shown as being off. I have to turn it "on" and then off again.
Bug Timeline
I think it occurs after i run a print that I manually paused or paused in the G-code.
Expected behavior
No response
Actual behavior
No response
Steps to Reproduce
No response
Version of CR6Community Firmware
v6
Printer model
Creality CR-6 SE
Motherboard
Creality v1.1.0.0-ERA
Display
Creality CR-6 stock touch screen
Mods
No response
Add-ons
No response
Bed Leveling
None
Your Slicer
Prusa Slicer
Host Software
None
The text was updated successfully, but these errors were encountered:
MattTheRoboMan
changed the title
[BUG] turning off beep when scree is touched
[BUG] turning off beep when screen is touched
May 7, 2024
Did you test the latest
extui
code or prerelease?Yes, and the problem still exists.
Bug Description
I have the beeper turned off in the printer settings so that it does not beep every time I touch the screen. However, after running prints that have been paused, the beeper will turn back on when I touch the screen. When I go into the settings, the beeper is shown as being off. I have to turn it "on" and then off again.
Bug Timeline
I think it occurs after i run a print that I manually paused or paused in the G-code.
Expected behavior
No response
Actual behavior
No response
Steps to Reproduce
No response
Version of CR6Community Firmware
v6
Printer model
Creality CR-6 SE
Motherboard
Creality v1.1.0.0-ERA
Display
Creality CR-6 stock touch screen
Mods
No response
Add-ons
No response
Bed Leveling
None
Your Slicer
Prusa Slicer
Host Software
None
The text was updated successfully, but these errors were encountered: