Aline Gondim Santos authored 3 years ago and Sébastien Blin committed 3 years ago

GitLab: jami-project#855
Change-Id: I7b2b2b76310743b7b330bfa4c1f123306288b1fa

Aline Gondim Santos authored 3 years ago and Sébastien Blin committed 3 years ago

In order to allow file/screen sharing from a audio only call, we must use requestmediachange to add this new stream.
deprecates setinputfile() and setDisplay(). Those functions should be replaced by requestmediachange().

GitLab: client-qt#499
Change-Id: I504789696fe050e360c775692c08ca86b47dd06a

Kateryna Kostiuk authored 3 years ago and Sébastien Blin committed 3 years ago

Change-Id: I8f1e181a4ce0e9930ada1f35019ca03fbe65b8d0

cf #492

Change-Id: Ieb922ad29136b5f607c2fc0086fa4cfd120a9bfb

Change-Id: Icaaf1f1628a1bd0b8f3fe1992424abb4d2b60bf3

find() returns an iterator that must not change

Change-Id: I02650ba17149be1bad002b754f459e8664746fc1

Change-Id: Id07b19bfc169d8cfa150f4469c4d333e75ac1bbe

Kateryna Kostiuk authored 3 years ago and Kateryna Kostiuk committed 3 years ago

Change-Id: I7ed7cbe07d087ec6cad22b0d53838c88d431de83

Change-Id: If7a6b8730f371b7ff66e4b8767e5affd64c4d264

Change-Id: I65907e052015efeef066d6262e6f179a4e4a1644

Change-Id: Ic83e090c19f3c5c7dc0c5d950ccb57411f217294

jami-client-qt#550

Change-Id: Ib4366178408171ab54a57508ad4fe2311b18fd95

+ trigger the emission of dataChanged signals when updating an
  interaction's data including a synthetic status change to notify
  the UI to update the progress of a transfer
+ add the transfer display name as a message list model role

Change-Id: I82b756e193e739c78502ef31702500d9f21a727c
Gitlab: #479

Trevor Tabah authored 3 years ago and Andreas Traczyk committed 3 years ago

This patch allows the client to use a listview to display chat
messages.

Gitlab: #479

Change-Id: I45ccbdbebe212299c4d477b69218e273014a3bd2

Change-Id: I786e9924a79427d81e3f8f3e9138ca494df53577

Change-Id: I3a320c8f58633a2bfb271ff513732e53a0335d5a

Kateryna Kostiuk authored 3 years ago and Sébastien Blin committed 3 years ago

This reverts commit bbda1066.

Reason for revert: <prevent contact removal for one_to_one>

Change-Id: I88dfa67def9af9d1bd517384df48d1f59e4c34a6

Compress the image to a value under 48k to be able to send it
through the DHT.

Change-Id: I4eee67e0a667bb278d2099abaf5305ca0a767efc

+ use QFileLock on profiles to avoid any potential problems with
parallel updates
+ Do not update write files if nothing is updated

Change-Id: Iff1e1ac6a0363a0531f67d0e3a40ee99fa67a32d

Amin Bandali authored 3 years ago and Adrien Béraud committed 3 years ago

Change-Id: I948ea21e577d4ff9ccd69bfb22261432be7ba8b4

Change-Id: Ifaa93b3e92c5c932b18a83758c45ea48878e3cfb

Change-Id: I07633e7e1d6b689af30b38648d6c2d354cf2c029

Logic is handled by the daemon, nothing to do for removeConversation

Change-Id: I4bdf41c5d7d21cfd523409602004b668627ecadc
GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282

Change-Id: I22b4fe8cd05d7f9c6b29f78fa00c6327f418032b

if there is other conversations with a contact, only the conversation
is removed, not the others

Change-Id: I6a7aa6fc4953c34fb46e68c7682d1891511b0017

After a sync, contactAdded will be emitted. But lrc was generating
a new conversation without the "added" information stored by the
daemon. Causing a smartlist with incorrect informations.

Change-Id: I5f05a905e831ec06353002fed40be403e3c753da
GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282

Change-Id: Ic1dca07904907ba9cfaefdc6b4a2df3737a97c50

Change-Id: I68fcfca5abff072741ae9e28cab44b29640b270d

Change-Id: I72e58f8aef09c07752169fbbc6194a2ef33b36d5

Change-Id: Ife955833aeb2cbfdbbeab0124558cbbcfe0ca6c7

Change-Id: I9679df3bda97d4401ea137088d006820154d141b

without it jami-client-gnome won't build

Change-Id: Ife26e5820a20740f6972bb70346e14e0489d6ba0

Use a few more accurate variable names, remove some redundant or old
logic, and better choice of displayed best name or id (also depends on
client-side change).

Change-Id: Iddd5d03649537813143a91702da521e631e1b2f2

Sébastien Blin authored 3 years ago and Amin Bandali committed 3 years ago

avoid changing the display.

Change-Id: If58239293bd2675064c694e32861cbae623ef163
GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282

Sébastien Blin authored 3 years ago and Andreas Traczyk committed 3 years ago

Change-Id: I8e9e55951de044065e7e4540606c107246e67bb7

This makes sense only in one to one. For swarm, there will be no
read only as we can add a new conversation member. Also, we should
not see readOnly = true for conversations with self.

Change-Id: Ic404a6b58e7812fedfe2fede91beb77b44436526
GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282

Change-Id: I6c16d3bd9890ce962c978a2aa1ac0a529deb9b27

Change-Id: Iba7814b2f849de7ac2424312c9460286e19f5fc5

Consider a conversation's read-only attribute when querying for indices
that match a given uri. This is done when searching for a conversation
associated to an interaction(in the rare case that more than one 1to1
conv exists).

Also remove all the conversations for a contact once the contactRemoved
slot is called.

Gitlab: #475
Change-Id: I637dbcf677a5e00b6b52320c3cd24fcd08cfacd6

GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282
Change-Id: Ie90a520acf900c5053ddbca980ff5b5bba3dcd63