-
cal0pteryx
nicoco, it's great to see so many contributions! :) you know about the storage branch and that the focus currently lies on getting this completed. It may feel like all other work, especially MRs, is stalled at the moment, but that should change after this giant task has been completed :)
-
nicoco
cal0pteryx, I am aware that the priority in on the new db layout and I'm thrilled about it, especially since it is the blocker for reactions and replies :)
-
nicoco
I'm having fun customising my gajim and opened the PRs so that no work is duplicated. I realize some will need some refactoring after the new DB layout is done :)
-
tagomago
Hi everyone! I'd like to ask: if you click on a conversation that has unread messages, is there any option to position the conversation view at the first unread message, instead of at the end of the conversation? Thx!!!
-
cal0pteryx
tagomago: not yet, but maybe soon
-
tagomago
Thanks a lot, cal0pteryx!
-
kurion
I am facing a weird behavior; might be missing something
-
kurion
the `is_encrypted` property of `OutgoingMessage` becomes true when the message is encrypted with OMEMO for a BareContact
-
kurion
but when I send an OMEMO encrypted message in a groupchat, the `is_encrypted` property seems to be false, although it was indeed encrypted.
-
kurion
in both cases the following try block from `send_message`in `client.py` has succeded ``` if method == 'OMEMO': try: self.get_module('OMEMO').encrypt_message(message) ```
-
kurion
How come the `is_encrypted` property becomes True when the message is to be sent to a BareContact (as expected) but remains False in case of GroupchatContact?✎ -
kurion
How come the `is_encrypted` property becomes True when the message is to be sent to a BareContact (as expected) but remains False in case of a GroupchatContact? ✏
-
lovetox
its not needed because groupchat messages are just sent without doing anything in the gui
-
lovetox
the muc will reflect the message and we will process it at that point
-
lovetox
this is different for single chat messages because we dont have a reflection so we need to store all infos when sending the message
-
kurion
Oh, I see
-
kurion
Actually, I was checking this because I wanted different sounds for encrypted and unencrypted messages.✎ -
kurion
Actually, I was checking this because I wanted different sounds for encrypted and unencrypted messages (sent messages from me as well as received messages) ✏
-
kurion
it was quite easy for BareContacts, but couldn't make it work with Groupchats due to the`is_encrypted` property not being set appropriately.
-
kurion
how/where should I set `is_encrypted` so that I can rely on this property to play different sounds in main.py?✎ -
kurion
how/where should I set `is_encrypted` so that I can rely on this property to play different sounds in `_on_message_sent` in main.py? ✏
-
kurion
Couldn't find exactly where `is_encrypted` is assigned a value in the case of BareContacts
-
kurion
I added a boolean `is_encrypted` to MessageSent dataclass
-
kurion
and set it when raising the event from client.py ``` app.ged.raise_event( MessageSent(jid=message.jid, account=message.account, message=message.message, is_encrypted=message.is_encrypted, ... ```✎ -
kurion
and set it when raising the event from `_send_message` in client.py ``` app.ged.raise_event( MessageSent(jid=message.jid, account=message.account, message=message.message, is_encrypted=message.is_encrypted, ... ``` ✏
-
kurion
and I can check that in main.py. Different sounds are working for BareContacts but not for Groupchats