Inconsistencies: Partial visible chats not rendered only at top side of screen; light off: Keyboard fades while screen is instantaneous. #137

New Issue

2026-10-27T15:40:29+01:00

adam commented

2026-10-27 15:40:29 +01:00

Ahoj,

I am on LilyGo T-Deck Plus, firmware version 0.9.10.

I see the following inconsistencies -- not really "bugs", but maybe you want to know:

When in the "Msgs" screen in the "channels" or "DMs" view, and there are more channels than fit on the screen, I can scroll.
When I scroll:
- At the bottom: Partly visible channels are rendered within their box partly (as it fits on the screen).
- At the top: Channels within their boxes which would be partly visible are not rendered at all; they abruptly appear as soon as they would fit fully on the screen.
In the "Contacts" view it is different again: There partly visible contact boxes are rendered on both side of the screen partly as they fit on the screen.

When pressing the trackball to switch off the screen, the screen's backlight switches off instantaneously, while the keyboard's backlight fades out.

Regards!

Ahoj, I am on LilyGo T-Deck Plus, firmware version 0.9.10. I see the following inconsistencies -- not really "bugs", but maybe you want to know: 1. * When in the "Msgs" screen in the "channels" or "DMs" view, and there are more channels than fit on the screen, I can scroll. When I scroll: - At the bottom: Partly visible channels are rendered within their box partly (as it fits on the screen). - At the top: Channels within their boxes which would be partly visible are not rendered at all; they abruptly appear as soon as they would fit fully on the screen. * In the "Contacts" view it is different again: There partly visible contact boxes are rendered on both side of the screen partly as they fit on the screen. 2. When pressing the trackball to switch off the screen, the screen's backlight switches off instantaneously, while the keyboard's backlight fades out. Regards!

adam closed this issue

2026-10-27 15:40:29 +01:00

adam commented

2026-10-27 15:40:30 +01:00

Point 2;
you mean, it would be nice to have a "fade-out" effect for the display too?

Point 2; you mean, it would be nice to have a "fade-out" effect for the display too?

adam commented

2026-10-27 15:40:31 +01:00

On Fri, 06 Mar 2026 12:01:51 -0800, @dabeani wrote:

you mean, it would be nice to have a "fade-out" effect for the
display too?

In general, I am not a fan of those effects at all. My preference is no
effect at all (also keeps the code cleaner).

Interestingly, in v0.9.9 the screen also had a fade out effect, which
disappeared in v0.9.10.

But, yeah, this is your design decision which way you go, I just pointed
out inconsistencies in the current implementation :-).

On Fri, 06 Mar 2026 12:01:51 -0800, @dabeani wrote: > you mean, it would be nice to have a "fade-out" effect for the > display too? In general, I am not a fan of those effects at all. My preference is no effect at all (also keeps the code cleaner). Interestingly, in v0.9.9 the screen also had a fade out effect, which disappeared in v0.9.10. But, yeah, this is your design decision which way you go, I just pointed out inconsistencies in the current implementation :-).

adam commented

2026-10-27 15:40:32 +01:00

a ok understood!
yea, i had this implemented for the screen but was not that happy with it from the implementation. Instead of redesign i removed it - but for the keyboard, i liked it.

Feedback is important, therefore i am asking for ideas!
I will park the 2nd topic right now - i will work on the other stuff to improve/fix.

Point 1 is fixed in v0.9.11!

a ok understood! yea, i had this implemented for the screen but was not that happy with it from the implementation. Instead of redesign i removed it - but for the keyboard, i liked it. Feedback is important, therefore i am asking for ideas! I will park the 2nd topic right now - i will work on the other stuff to improve/fix. Point 1 is fixed in v0.9.11!

adam commented

2026-10-27 15:40:32 +01:00

Point 1 is fixed in v0.9.11!

Nice!

Actually, so since it behaved differently in the "Contacts" and in the "Msgs" screen, do you have different/ duplicate code which actually does the same thing: Handle rendering of items in a scrollable screen?

You could save code and maintanance effort to have one single piece of code doing that ;-).

I will park the 2nd topic right now

And since you indicated that it actually was your intentional choice due to aesthetic preferences and not a mistake, I close this issue.

> *Point 1 is fixed in v0.9.11!* Nice! Actually, so since it behaved differently in the "Contacts" and in the "Msgs" screen, do you have different/ duplicate code which actually does the same thing: Handle rendering of items in a scrollable screen? You could save code and maintanance effort to have one single piece of code doing that ;-). > *I will park the 2nd topic right now* And since you indicated that it actually was your intentional choice due to aesthetic preferences and not a mistake, I close this issue.

adam commented

2026-10-27 15:40:33 +01:00

Point 1 is fixed in v0.9.11!

Actually, not.

So I reopen this issue.

The "Discovered" screen acts the same as the "Msgs" screen.

> Point 1 is fixed in v0.9.11! Actually, not. So I reopen this issue. The "Discovered" screen acts the same as the "Msgs" screen.

adam commented

2026-10-27 15:40:34 +01:00

Fixed in v0.9.14.

Fixed in v0.9.14.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/meshcore#137