When I am reading a long message on DeltaTouch, having clicked on the “Show full message…” link, I get booted out to the end of the chat if a notification comes in. This is only really annoying if I have several long messages, and must scroll-click-scroll to resume reading.
Ping @lk108 if you haven’t seen it already :))
Should be reported as an issue, probably?
2 Likes
Do you click on the notification or do you swipe it away?
Neither is necessary: when the notification pops up, I am booted from the full message before I can do anything. If I neither swipe nor click, but just let the notification fade, it makes no difference.
And sorry, I should have pinged; thanks, Hocuri.
I can’t reproduce this. This happens on a Pinephone with Mobian/Phosh, right? Which versions?
I’m still on Bookworm, but I have DeltaTouch 2.22.0. It has happened repeatedly over some weeks, but is most noticable in a chat with an RSS bot; if you subscribe to a fulltext RSS, like theconversation.com, you get a string of long messages, which makes it more likely.
Perhaps the source of the notificatons matters? I think at least some of the notifications were from another profile, but some might have been RSS messages to the same chat. I will observe this more carefully and report back.
Which GNOME/phosh version do you have?
Sorry, GNOME 1:43+1, Phosh 0.24.0-1.
Strange, I really can’t reproduce it with the same setup. Does it happen every time you’re in the full message page and a notification comes in? And is the most recent message in the chat highlighted for a short time?
I think it happens everytime but couldn’t swear to it; if I were absorbed in what I was reading I might not consciously notice the notification popup. I am not sure about the highlighting. I will look for the highlighting, and check my notification log after reading full messages, which should tell me if I got notifications I did not notice.
Peripherally, I’ve noticed that the “Show full message…” link sometimes does not actually show more content. “Show full message (341 more words)” might be more useful, but it is longer-winded.
This happened again: the interrupting message was sent to a different profile, and I did not notice any highlighting. Sorry for the slow reports.
Ok, I tried again to reproduce this, and I can’t. DeltaTouch 2.22.0 with two profiles on a pinephone with Mobian/Phosh, versions as above. Sent a very long message to one of the profiles and clicked on “Show full message…”. Stayed on that page and scrolled up/down a bit while frantically sending messages to exactly this chat, other chats of that profile and the second profile present on the device. At no point was the page showing the full message auto-closed.
Also, I can’t see any code path that would close this page except when an incoming notification is activated. Are there ghost clicks with your touch screen?
Happened again; I’m afraid I tapped the notification automatically because it was over the text I was reading, but there was certainly no highlighting after I was booted to the chat containing the long messages. I was reading the last message at the time, so it did not scroll down.
Don’t worry too much about reproducing it, feel free to ignore this for a while as I keep poking at it and improving the description. The app is getting quite slow and has been updated through a lot of experimental versions; it may be behaving in an idiosyncratic manner.
I have not noticed ghost taps but can’t rule it out; there are sometimes minor sensitivity problems with the corners of the screen.
If I do tap the notification, is it supposed to take me to the new message?
If you do tap the notification, that would explain it.
If you tap the “View” bar of the notification, it should take you to the message and highlight it. If you tap the main body of the notification, phosh will send out a default action with which the app cannot do anything because it contains no info except for the text “default”. I think we discussed this before, as previously, a popup just showing “error” would appear. The popup has been removed, but there’s actually code that will close the window. I’ll remove it.
Well, performance could surely be improved, updated through experimental versions or not
PR to fix this: #130 - fix: only clear extraStack if really needed - lk108/deltatouch - Codeberg.org
CI build, if you want to try it: https://codeberg.org/lk108/-/packages/generic/deltatouch/pr130/files/5481630
Note that it will take you to v2.25.0 from which going back to v2.22.0 is not supported.
EDIT 2: It works on my device. but you have to install libkf5archive5 first. This will enable you to export your keys again (but I don’t know how long this will be possible in DC in general)
Thank you very much, I will certainly test that! I’m rather depending of DT at the moment so it may be some days. That said, while I’ve been consistently backing up, I’ve never yet had downgrade-forcing issues.
I’m sorry this was so much effort to debug, I should have observed a bit more before reporting; I could have seen which notifications has been dismissed in the notifications menu. Too-late detail; if I am in the add-attachment menus and get a notification, it also drops back into the chat.
From what link2xt said, I got the impression that there are no plans to remove key export, though of course it is advanced functionality and will stay deep in the UI where it can be found but not stumbled over.
No need to be sorry! It was actually a shortcoming in the code, only discovered due to your reports here.
1 Like