adam/meshcore
1
0 Fork 0
mirror of https://github.com/dabeani/meshcoreterm.git synced 2026-11-02 02:55:46 +01:00
Code Issues 97 Packages Projects Releases Wiki Activity

Quick Reply sent message was not shown in chat; tapping on another message did open my not-shown sent message. #230

New Issue
Closed
opened 2026-10-27 15:44:56 +01:00 by adam · 4 comments
adam commented 2026-10-27 15:44:56 +01:00
Owner
Copy link
Copy source

Describe the bug

Within a public channel, I had experienced the following:

I did send a Quick reply with placeholders.

This was not shown in the message list.

I did it again.

Still not shown.

Then I observed, that when in the message list I tapped on a message, actually other messages did open than what I tapped on -- I could open the message I sent which was not shown in the message list by tapping on the next message, which was received at almost the same time thatn I sent my message.

The issue of tapping registered wrongly has now resolved by itself, the Quick Reply messages I sent are still not shown. Also, I cannot reproduce: Now, the Quick Reply is actually shown. So I cannot do deeper testing.

Which device are you using

LilyGO T-Deck Plus

Which Firmware are you using

v0.9.12

**Describe the bug** Within a public channel, I had experienced the following: I did send a Quick reply with placeholders. This was not shown in the message list. I did it again. Still not shown. Then I observed, that when in the message list I tapped on a message, actually other messages did open than what I tapped on -- I could open the message I sent which was not shown in the message list by tapping on the next message, which was received at almost the same time thatn I sent my message. The issue of tapping registered wrongly has now resolved by itself, the Quick Reply messages I sent are still not shown. Also, I cannot reproduce: Now, the Quick Reply is actually shown. So I cannot do deeper testing. **Which device are you using** LilyGO T-Deck Plus **Which Firmware are you using** v0.9.12 <!-- github-sync-id:4343319961 -->
adam closed this issue 2026-10-27 15:44:56 +01:00
adam commented 2026-10-27 15:44:57 +01:00
Author
Owner
Copy link
Copy source

fixed now in v0.9.12.1

  • Messages: align on-device channel transcript tap/hold hit-testing with the timestamp-sorted rendered rows and unread separator so Quick Reply echoes stay selectable as the visible message instead of opening a different hidden row (#230).
fixed now in v0.9.12.1 - Messages: align on-device channel transcript tap/hold hit-testing with the timestamp-sorted rendered rows and unread separator so Quick Reply echoes stay selectable as the visible message instead of opening a different hidden row (#230). <!-- github-comment-id:4339241841 -->
adam commented 2026-10-27 15:44:58 +01:00
Author
Owner
Copy link
Copy source

Heyho,

fixed now in v0.9.12.1

What was actually the issue that the message I did sent was not visible in the chat?

Heyho, > *fixed now in v0.9.12.1* > > * *Messages: align on-device channel transcript tap/hold hit-testing with the timestamp-sorted rendered rows and unread separator so Quick Reply echoes stay selectable as the visible message instead of opening a different hidden row ([Quick Reply sent message was not shown in chat; tapping on another message did open my not-shown sent message. #230](https://github.com/dabeani/meshcoreterm/issues/230)).* What was actually the issue that the message I did sent was not visible in the chat? <!-- github-comment-id:4343899150 -->
adam commented 2026-10-27 15:44:59 +01:00
Author
Owner
Copy link
Copy source

There is a hidden line separator, which will show up for a short time when you scroll to the newest messages. This caused issues with the reply function and mixed the messageidx.

There is a hidden line separator, which will show up for a short time when you scroll to the newest messages. This caused issues with the reply function and mixed the messageidx. <!-- github-comment-id:4349995339 -->
adam commented 2026-10-27 15:44:59 +01:00
Author
Owner
Copy link
Copy source

Closing, although I can not reliably test this.

Closing, although I can not reliably test this. <!-- github-comment-id:4605150475 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshcore#230