Bug 478463

Summary: When sending a text, the screen scrolls all the way to the top so only the last message sent or received is visible.
Product: [Applications] kdeconnect Reporter: Daniel Remsburg <danielremsburg>
Component: messaging-applicationAssignee: Simon Redman <simon>
Status: RESOLVED DUPLICATE    
Severity: minor    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Daniel Remsburg 2023-12-13 01:32:46 UTC 
SUMMARY
Problem with SMS Text app scroll hiding message history.

STEPS TO REPRODUCE
1.  Use the app
2. 
3. 

OBSERVED RESULT
When you send a message, the screen automatically scrolls all the way (down?) so the message you just typed goes all the way to the top. You can't see what the other person just typed or any of the history unless you manually grab the scroll bar and scroll back up (mouse wheel seems not to be working). 

This is incredibly annoying, especially if you both type messages at the same time or you haven't read their message yet. Essentially I have to keep scrolling back up all the time unnecessarily. Also, sometimes I keep a running conversation with someone and I have to scroll back up to read what was said, also unnecessarily annoying. Nearly every other SMS application out there will just let your messages scroll naturally and you can see as many as can fit on the screen without scrolling around. 

I have tried to find settings or preferences to disable this behaviour but there seems to be no settings or preferences.

Also, as a side note, I can code but I can't (won't?) spin up the while entire build system for this, is there a way I can contribute otherwise?


SOFTWARE/OS VERSIONS

KDE Connect SMS 23.08.1
Ubuntu Studio 23.10
KDE Plasma 5.27.8
KDE Frameworks: 5.110.0
Qt: 5.15.10
Linux Kernel: 6.5.0-14-lowlatency (64 bit)
Graphics Platform: X11
Comment 1 Simon Redman 2023-12-14 05:08:46 UTC 
> as a side note, I can code but I can't (won't?) spin up the while entire build system for this, is there a way I can contribute otherwise?

As mentioned in the bug to which I am linking this one, a key missing piece of information is what exact situation causes this behavior to happen. From the way you've worded this bug, it appears it happens to you all the time, but that is not my experience nor the experience of the other reporter.

That said, developer time is always the limiting resource. Even if we knew exactly what needed to be fixed, fixing it would require allocating time that doesn't currently exist.

*** This bug has been marked as a duplicate of bug 477361 ***