-
-
Notifications
You must be signed in to change notification settings - Fork 373
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
Driver OTPW cannot be cleared or ignored #1955
Comments
@sbtoonz pls post a video... |
5.Printing.-.ETA_.07_31.PM.-.Corner.Skirt.X2_ASA_8h35m.gcode-.Trident.-.Google.Chrome.2024-08-05.08-56-15.mp4 |
@sbtoonz pls try a reload without cache (ctrl + shift + f5 on windows) |
6.Printing.-.ETA_.07_32.PM.-.Corner.Skirt.X2_ASA_8h35m.gcode-.Trident.-.Google.Chrome.2024-08-05.08-59-22.mp4 |
force cache reload not yielding any different outcome |
ohhh... @sbtoonz pls check the PR for this bug itself. this one is not even merged yet (waiting for a review) and therefore not yet released! (and the initial bug report also describe, that this issue is in v2.12.0) |
Ah I'll pull this down then :) |
You can download a build from the ci chain. |
Mainsail Version:
2.12.0
Browser:
Chrome
Device:
Desktop PC
Operating System:
Windows
What happened?
A lot of buttons that do nothing. This seems unintentional.
driver-temp-warning.mp4
It would be nice if they worked. Currently you cannot avoid this warning if you want to get the maximum out of a set of 2209 sticks for example, and as such this is just an annoyance and not very helpful.
What did you expect to happen instead?
The notification to be dismissed / ignored, or worst case scenario that the buttons were disabled.
How to reproduce this bug?
Either generate the OTPW flag on a driver, or just unconditionally push it to the notification list in the client code since it's a mainsail-only implementation.
Additional information:
No response
The text was updated successfully, but these errors were encountered: