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

F1rstLayer_Touchscreens | Bed PID temperature displays keyboard off-screen, numeric input not possible #313

Open
ELynx opened this issue Dec 5, 2024 · 1 comment

Comments

@ELynx
Copy link

ELynx commented Dec 5, 2024

Description

F1rstLayer_Touchscreens Firmware
Calibration-PID tuning -> Bed PID -> Degrees C setting -> Keyboard is displayed shifted left, numeric input is not possible

Ender3 Pro with 4.2.7 board, CRTouch, Touchscreen firmware 7.4.9
firmware_Ender3_427_BLT_DW7.4.9.bin + F1rstLayerDwinPT_480272_20240127.7z

Clicking 70 for Bed PID displays touch keyboard shifted far to the left, only part of rightmost key column is visible. UI is responsive, it is possible to close keyboard with (X).
At the same time Nozzle PID settings (clicking 170) displays keyboard correctly.

Steps to Reproduce

  1. Start the printer
  2. On touchscreen, use item "Tools"
  3. On touchscreen, use item "PID Tuning"
  4. On touchscreen, click on Bed PID temperature setting (default 70)

Expected behavior: Touch keyboard is displayed centered, numeric input is possible.

Actual behavior: Touch keyboard is displayed shifted left, only rightmost key column is visible. It is possible to close keyboard with partially seen (x) key => it is not possible to change the setting. Nozzle PID setting displays keyboard correctly.

Additional Information

Also tested with screen rotated 180 degrees via settings, issue is the same (sans rotated).

UI use can be resumed, since (x) is partially visible. PID calibration process for both Nozzle and Bed are usable.

https://www.youtube.com/watch?v=Zq2_2FQZgLA

1
2
3

@ELynx
Copy link
Author

ELynx commented Dec 5, 2024

More personal message on the issue: I looked at the source code, but codebase will require some time for me to get into it, so I cannot find an obvious bug immediately. Knowing my patterns, I can "disappear" from the topic for some months, so I make this public rather than silently trying to fix this with unknown chance of success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant