Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

If Tune from a Paused Print, then Back from Tune Returns User to Screen 37 instead of Screen 39 #220

Closed
Thinkersbluff opened this issue Mar 15, 2021 · 2 comments
Labels
area:dwin-interop Area - DWIN interop t:bug Something isn't working

Comments

@Thinkersbluff
Copy link

Description

If User selects Pause on the Printing Screen, and then selects Tune, when they select Back to return to the Printing (Paused) screen, they are instead returned to the Printing Screen. There is no "Resume" button, but there is a "Pause" button. To restart the print, the User has to Pause it again & Confirm, to get back to the Resume button.

Steps to Reproduce

  1. Start a new print
  2. Select Pause and Confirm Pause
  3. Select Tune
  4. Select "Back"
  5. User is returned to screen 37 instead of screen 39

Expected behavior:

Back from the Tune screen in this instance should return the user to screen 39.

Actual behavior:

Back instead returns the user to screen 37.

Additional Information

Using BTT SKR CR6 v1.0 motherboard with stock TFT, running the 11 March Nightly firmware and the btt-w/stock-creality-tft config files.

Current work-around is to select "Pause" again, Confirm Pause again, then use Resume to restart the print.

@Sebazzz Sebazzz added the t:bug Something isn't working label Mar 15, 2021
@Sebazzz Sebazzz added this to the Community Firmware Release 6 milestone Mar 15, 2021
@Sebazzz Sebazzz added the area:dwin-interop Area - DWIN interop label Mar 15, 2021
@Sebazzz
Copy link
Collaborator

Sebazzz commented Mar 15, 2021

I sneaked a possible fix for this in 38dc92b - since you are compiling yourself now, can you test that? (Note that the commit involves CR6Community/CR-6-touchscreen#40 so you need to reflash the touch screen as well)

@Thinkersbluff
Copy link
Author

I sneaked a possible fix for this in 38dc92b - since you are compiling yourself now, can you test that? (Note that the commit involves CR6Community/CR-6-touchscreen#40 so you need to reflash the touch screen as well)

Sorry - just found this a little while ago.

I tried the latest, but I see it is presently LOCKED according to Discord.
Bug is still present.
Also note that if I select Screen Saver OFF, I get a dotted line box instead of OFF and can not turn it back on again.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
area:dwin-interop Area - DWIN interop t:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants