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

[BUG] Confirming status screen parameters using touch on TFT_COLOR_UI resets them to 0 #20210

Closed
onfoot opened this issue Nov 19, 2020 · 5 comments · Fixed by #20213
Closed

Comments

@onfoot
Copy link
Contributor

onfoot commented Nov 19, 2020

Bug Description

When opening bed, nozzle temperature, or fan speed setting from the status screen on TFT_COLOR_UI running on TS35, tapping on the checkmark to confirm the setting sets it to 0, even if they are set to a non-zero value.

It works properly when accepting the setting using the rotary encoder.

Doesn't matter whether the value is changed using the rotary encoder, the slider, or the + button. Only the way of accepting the setting results in different behavior.

Configuration Files

Config.zip

Steps to Reproduce

  1. Tap bed temperature setting from status screen
  2. Change to 50
  3. Tap checkmark to confirm

Expected behavior:

Bed temperature is set to 50

Actual behavior:

Bed temperature is set to 0

Additional Information

Video

@onfoot onfoot changed the title [BUG] Confirming bed temperature on TFT_COLOR_UI sets it to 0 [BUG] Confirming status screen parameters using touch on TFT_COLOR_UI resets them to 0 Nov 19, 2020
@rhapsodyv rhapsodyv self-assigned this Nov 19, 2020
@rhapsodyv
Copy link
Member

Are you using last bugfix?

I tested it and worked for me.

@Section59
Copy link

Section59 commented Nov 20, 2020

Having this issue also using #define MKS_ROBIN_TFT35 - Setting it via octoprint seems to work, and shows on the screen as the correct set temp.

Applys to any settings i can change, reverts all to their lowest setting. compiled using latest bugfix version.

@rhapsodyv
Copy link
Member

Ok, found it. Fixed: #20213

@onfoot
Copy link
Contributor Author

onfoot commented Nov 20, 2020

Fix verified. 🥳

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants