https://bugs.kde.org/show_bug.cgi?id=476747
Bill <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from Bill <[email protected]> --- (In reply to Dylan Hall from comment #5) > Also having this issue often, because it completely loses the message i've > just typed, it has a much higher impact than it needs to. > > A change could simply be, don't clear the input until the app confirms with > the phone that it has been recieved - if it's disconnected, show an error, > and leave the message. > > If the issue is the connection we're using to send doesn't provide > confirmation, a workaround might be: > > * attempt send > * attempt refresh and look for the message in the chat log > * if it exists, clear the input, otherwise leave it and show an error > > this would at least save completely rewriting a message from scratch, or > seeing the input clear and assuming a message has sent when it hasn't. I think this is the best idea to minimize the impact of the connection detection lag and downstream issues from it. What I like about Dylan's approach is that (as far as I can tell at this time) it won't impact future more robust improvements to the ping/pong features of the app, meaning we shouldn't need to rip this fix out later since it's just saying: Send the message, do you see it in the chat (did gotNewMessage fire)? Yes? Cool, clear the input. No? Don't clear the input. I just did a PoC on this and it works like a champ. Right now it's just 4 small changes to one file. I'm going to do some more cleanup, and more extensive testing. If this fix passes muster, ima push it. -- You are receiving this mail because: You are watching all bug changes.
