Text editing (T-Deck): Text does not scroll, past text has to be edited blindly. #114

Closed
opened 2026-10-27 15:39:18 +01:00 by adam · 4 comments
Owner

This is a follow up to here. Since I can't reopen issue #85, I create a new one:

The trackball on T-Deck now scrolls the cursor, but when the cursor goes to the left past the currently visible text, the text does not scroll.

So one has to blindly edit the text.

Actually, the text should also scroll.

And to make editing easier, I suggest smaller font size, maybe a message input box that wraps to a new line as well.

Firmware version v0.9.10.

Regards,
and P.S.:

Since this is something which could easily be spotted by testing, and also relating to the issue that v0.9.10 broke update over Wifi(?), I am wondering:
Are enhancement wishes and bug reports fed to an LLM, which generates patches, that are applied and then a new version is shipped without proper testing of the feature/ fix?

Regards!

This is a follow up to [here](https://github.com/dabeani/meshcore/issues/85#issuecomment-38722890240). Since I can't reopen issue #85, I create a new one: The trackball on T-Deck now scrolls the cursor, but when the cursor goes to the left past the currently visible text, the text does not scroll. So one has to blindly edit the text. Actually, the text should also scroll. And to make editing easier, I suggest smaller font size, maybe a message input box that wraps to a new line as well. Firmware version v0.9.10. Regards, and P.S.: Since this is something which could easily be spotted by testing, and also relating to the issue that [v0.9.10 broke update over Wifi(?)](https://github.com/dabeani/meshcore/issues/113), I am wondering: Are enhancement wishes and bug reports fed to an LLM, which generates patches, that are applied and then a new version is shipped without proper testing of the feature/ fix? Regards! <!-- github-sync-id:3975092363 -->
adam closed this issue 2026-10-27 15:39:18 +01:00
Author
Owner

smaller font size in the input box, and a second line with scrolling possibilities are implemented with v0.9.11.
Due to lack of time, i did not invest too much time for testing. Lets see if i can handle this better in future.

Sure, AI is our friend.

smaller font size in the input box, and a second line with scrolling possibilities are implemented with v0.9.11. Due to lack of time, i did not invest too much time for testing. Lets see if i can handle this better in future. Sure, AI is our friend. <!-- github-comment-id:3941619220 -->
Author
Owner

On Sun, 22 Feb 2026 12:02:10 -0800, @dabeani wrote:
(dabeani/meshcore#114)

Due to lack of time, i
did not invest too much time for testing. Lets see if i can handle
this better in future.

I see that you react very quickly. This is not important. If you do not
have the capacity, it is just fine to take things more slowly and give
it the time it needs.

And I think, more well-tested or implemented improvements and fixes
would also lead to less (follow-up) reports.

Regards and thanks for your effort for the software!

On Sun, 22 Feb 2026 12:02:10 -0800, @dabeani wrote: (dabeani/meshcore#114) > Due to lack of time, i > did not invest too much time for testing. Lets see if i can handle > this better in future. I see that you react very quickly. This is not important. If you do not have the capacity, it is just fine to take things more slowly and give it the time it needs. And I think, more well-tested or implemented improvements and fixes would also lead to less (follow-up) reports. Regards and thanks for your effort for the software! <!-- github-comment-id:3943837408 -->
Author
Owner

Due to lack of time, i did not invest too much time for testing. Lets see if i can handle this better in future.

Sure, AI is our friend.

I am not a software developer, and what I have heard is that especially when using LLMs to add functionality or fix issues, it is important to write a test for every functionality (which tests if the functionality works as specified), and have those tests running automatically. So if something breaks something else would be catched.

Maybe that can help in the longer term.

Regards!

> *Due to lack of time, i did not invest too much time for testing. Lets see if i can handle this better in future.* > > *Sure, AI is our friend.* I am not a software developer, and what I have heard is that especially when using LLMs to add functionality or fix issues, it is important to write a test for every functionality (which tests if the functionality works as specified), and have those tests running automatically. So if something breaks something else would be catched. Maybe that can help in the longer term. Regards! <!-- github-comment-id:3996210569 -->
Author
Owner

smaller font size in the input box, and a second line with scrolling possibilities are implemented with v0.9.11.

I can confirm.

Althouh not all text input fields got smaller font size, and the "two line" field is not really behaving how one would expect from a simple text editor, but it has at least basic functionality.

> smaller font size in the input box, and a second line with scrolling possibilities are implemented with v0.9.11. I can confirm. Althouh not all text input fields got smaller font size, and the "two line" field is not really behaving how one would expect from a simple text editor, but it has at least basic functionality. <!-- github-comment-id:4112595933 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshcore#114