!bfebJVBOZMnORmkVdO:matrix.org

SchildiChat Android

638 Members
Discussion about SchildiChat for Android | FAQ: https://schildi.chat/android/faq/ | Bugs: https://github.com/SchildiChat/SchildiChat-android/issues | Translations: https://translate.schildi.chat/projects/schildichat/schildichat-android/197 Servers

Load older messages


SenderMessageTime
29 Sep 2023
@ducheng:matrix.org@ducheng:matrix.orgRedacted or Malformed Event18:19:47
@ducheng:matrix.org@ducheng:matrix.orgRedacted or Malformed Event18:20:54
@spiritcroc:spiritcroc.deSpiritCroc banned @ducheng:matrix.org@ducheng:matrix.org.18:21:00
@spiritcroc:spiritcroc.deSpiritCrocHope I cleaned up enough, ping me/admins+mods if necessary18:22:10
@spiritcroc:spiritcroc.deSpiritCroc banned @nimilv:matrix.org@nimilv:matrix.org.18:23:19
30 Sep 2023
@windystone:matrix.orgwindystone joined the room.01:13:27
@miladfashi:envs.netmiladfashiWhy when I send a picture I can not see my pic in chat room until i close app and reopen it !?06:24:22
@mahamati:matrix.orgÙwÚ changed their display name from Freethought Shall Reign to ÙwÚ.10:26:49
@mahamati:matrix.orgÙwÚ changed their profile picture.10:27:22
@kim:sosnowkadub.deHarHarLinks

I'm having the issue that when I have an unread noisy notification, any other notification will also be noisy indirectly

I realize but that only gets security fixes anymore

12:47:07
@kaki87:chat.kaki87.netKaKi87Hello, when trying to write a message in this channel on mobile, the app suddenly turns blank white, is that a known issue ? Thanks19:02:23
@nderumig:blabla.thecamionnetteproject.frNicoThat happens sometimes with me as well20:06:31
@nderumig:blabla.thecamionnetteproject.frNicoJuste reset the account / clear cache / try to open it on two different devices at the same time20:06:54
@nderumig:blabla.thecamionnetteproject.frNico* Just reset the account / clear cache / try to open it on two different devices at the same time21:45:41
1 Oct 2023
@kuniyahakeem:matrix.orglove set a profile picture.06:20:51
@vbglufh:matrix.orgvbglufh joined the room.11:11:17
@danglerowner:matrix.orgdanglerowner joined the room.17:51:34
2 Oct 2023
@temp4096:matrix.orgtemp4096 joined the room.04:48:45
@mhzx:matrix.orgmhzx joined the room.12:59:01
@jdhdhe:matrix.org@jdhdhe:matrix.org joined the room.14:17:39
@jdhdhe:matrix.org@jdhdhe:matrix.org left the room.14:18:57
@pokon548:bukn.ukpokon548 joined the room.15:42:36
@anosomtoja:matrix.organosomtojaHi there I'm investigating a bug in SchildiChat and need some advice. If you reply to a message (quick reply or from menu, doesnt matter) the editText cursor will reset to the beginning and disappear (the editText view loses focus). I fixed the part where the cursor goes back. I tried to fix the bug where the cursor disappears by simply adding editText.showKeyboard(andRequestFocus = true) to renderSpecialMode in the PlainTextComposerLayout. Unfortunately this does nothing and the view loses focus anyway. Even if i force it to change back from a listener on the editText view it loses focus again (tested with a viewTreeObserver: after i manually focus the view, it loses the focus again and the new focused view is null). The only way to give it focus again is with user input (tapping the editText). The cause of this must be somehow related to setting visibility to the related relatedMessageGroup in the expand function (if i remove this line "views.relatedMessageGroup.isVisible = true" the editText doesn't lose focus). I also tried setting the relatedMessageGroup and its children to not be focusable but that did not help. Unfortunately I don't think it's possible to use a stack dump or similar to trace back to the root of the issue, so I need someone with a lot more experience in android development to clue me in as to what could be happening. Thanks in advance.15:49:40
@spiritcroc:spiritcroc.deSpiritCroc
In reply to @anosomtoja:matrix.org
Hi there I'm investigating a bug in SchildiChat and need some advice.
If you reply to a message (quick reply or from menu, doesnt matter) the editText cursor will reset to the beginning and disappear (the editText view loses focus). I fixed the part where the cursor goes back. I tried to fix the bug where the cursor disappears by simply adding editText.showKeyboard(andRequestFocus = true) to renderSpecialMode in the PlainTextComposerLayout. Unfortunately this does nothing and the view loses focus anyway. Even if i force it to change back from a listener on the editText view it loses focus again (tested with a viewTreeObserver: after i manually focus the view, it loses the focus again and the new focused view is null). The only way to give it focus again is with user input (tapping the editText). The cause of this must be somehow related to setting visibility to the related relatedMessageGroup in the expand function (if i remove this line "views.relatedMessageGroup.isVisible = true" the editText doesn't lose focus). I also tried setting the relatedMessageGroup and its children to not be focusable but that did not help. Unfortunately I don't think it's possible to use a stack dump or similar to trace back to the root of the issue, so I need someone with a lot more experience in android development to clue me in as to what could be happening. Thanks in advance.
I'm not sure what happens there, just some spontaneous idea would be that you could launch the showKeyboard() or whatever function to request focus with Handler.post() or Handler.postDelayed() so it's not run too early in the UI queue. May be better to discuss in a github issue than here though.
15:56:34
@anosomtoja:matrix.organosomtojaI'll try that and report back, thanks.15:58:18
@anosomtoja:matrix.organosomtojaUsing a delay fixes it, thanks. Although it would be nice to know what's going on.16:25:43
@spiritcroc:spiritcroc.deSpiritCroc
In reply to @anosomtoja:matrix.org
Using a delay fixes it, thanks. Although it would be nice to know what's going on.
Did Handler.post() without delay not work? In case a delay is necessary, then it's not really a proper fix but rather a hint what's going on (although I don't have an issue accepting something like that as workaround).
16:33:33
@anosomtoja:matrix.organosomtojaWorks without delay too16:39:52
@spiritcroc:spiritcroc.deSpiritCrocThen it's good, I recall having to do that as well in similar scenarios before, to ensure it's called at the right time.16:44:59
@h171655h:matrix.org@h171655h:matrix.org left the room.19:05:50

There are no newer messages yet.


Back to Room ListRoom Version: 5