Also, force the format of the vcard to always be the same to
avoid to change the shasum in a useless way.
Finally, only change if there is new details
https://git.jami.net/savoirfairelinux/jami-project/-/issues/1558
Change-Id: I95bc52e13c8d1020eae6ad64e77d4e58b1ee734b
This is impossible to follow correctly, causing weird things.
Now Body always contains the original Body from the libclient,
LinkifiedBody the linkified Body and Linkified is empty if the
message is not linkified.
Change-Id: I29e5f7cf1c5a2093f5e4b7785216e8b9b24e9ad8
GitLab: #961
Iterate through CPP elements and use positionView(ListView.Center)
as other approach seems bugguy or slower.
Change-Id: I43879969ccb457166879a156efb482e77ff07d6b
If a window changes its name, we should share the parent process windows.
This can happen with chrome, visual studio code and file explorer for example.
+ Fixes non opening SelectScreen window when Jami language changes.
Change-Id: Ib16992dde08e6a9fa191c9fb1cbc4efd304efe6d
Show notification when a peer is sharing its position on the non
current conversation.
This needed a lot of changes. Now we store shared position via
accountId + peer.
This also fix location icons and keep state when changing from
one account to another.
Change-Id: I8c1848890efa09f6e296e9da779a355167e4d3d4
GitLab: #888
+ Add call buttons to start a new call
+ React to events from the swarm
+ call interactions (Join call/Call ended, etc)
+ active calls area
+ Add call management logic in LRC
+ Feature is enabled via the experimental checkbox
https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/312
Change-Id: I83fd20b5e772097c0792bdc66feec69b0cb0009a
Handle application/edited-message type to support message edition.
Previous bodies are saved in the interaction to be able to get the
original post to avoid unwanted editions.
While loading a conversation, we store the editions in a temporary
map that we link once the edited message is detected. This work
because we can't edit a message before this message exists.
PreviousBodies in interaction.h contains every previous body detected
and the client can show previous version of the message in a popup.
Deleting a message works the same way, just that any message
with an empty body is not shown.
https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/316
Change-Id: Ib158abd16ad4b629532de11694e88d86a12d72a8
+ Remove "Accept files from unknown senders" because since swarm
we can't get files from non contacts are the conversation is not
cloned, and non swarm files are ignored
+ Rename "ignore the swarm" to "Mute conversation" as ignore is
unclear
Change-Id: Ifced8f8efe841e2345d50530ee313e6b95b35920
This is an older issue that has resurfaced where mobile device rotation
at the beginning of a call cause a frame-copy to a stale buffer because
the DecodingStarted event is handled asynchronously.
Noticed on Windows but I believe any non-dbus build should have it.
So we make all the connections blocking and adjust some parameters.
This commit also removes the DecodingStarted handler in CallModel which
was causing the client's target video frame to be reallocated for each
account present.
Change-Id: I23ac4e0bd4b446e7a532f0d362f7ecd209d3c790
GitLab: #536
Asking jami to launch another instance with ./jami-qt jami:xxx
will search for "xxx" inside the application and select the
conversation if found.
This allow to support webpage with <a href="jami:username">
For GNU/Linux, in the .desktop file, x-scheme-handler/jami is
added.
For packaging, we will need to determine if the scheme is handled
automatically. For now, to test, we need to add:
x-scheme-handler/jami=jami-qt.desktop;
in "~/.config/mimeapps.list" (and jami-qt.desktop) should
be in a valid path.
Change-Id: Ibbb6e8942f1873d81a57640bdf6f839885981be3
GitLab: #655
+ Update status for swarm
+ Show read status like android (right if 1 reader, under the bubble
if more)
+ Display a sending status
Change-Id: I653e3573c4dc75950cc274dd01859d9335e0177f
A signal exists for showing errors to the user to make failing cases
more explicit. With this patch, errors detected are displayed to
the end user so that they know that an error occured and what
kind of error occured.
Change-Id: Ib2d4d4fdb171235e0598de0f1c190b8fd0fcc336
+ Remove readOnly from conversation's as it was never used
and not necessary in multi swarm as you can re-add members anyway
so it's never read only.
+ Makes non swarm conversations just readable.
Users can save whatever they want and replace old non migrated
conversations to new swarm.
Change-Id: I8aa2521bc524b6159d7ba0b613834438e293e09e
The only missing case were for changing the current default camera.
Other methods can be removed.
Change-Id: I91fce779f4a41fe4d667444aea57b1b454aa702b
GitLab: #651
In a conference, with this patch, the user is able to share
a media while keeping the camera. The mute button for the camera
only control the camera and we use requestMediaChange to add medias.
To stop sharing a media, the user will click on the dedicated button.
If the peer is not compatible with multistream, the behavior will
be the same as before
https://git.jami.net/savoirfairelinux/jami-project/-/issues/1429
Change-Id: If5e0634be6d0d06900ad82554b32a524fd4db36c
