In the current implementation, the chatViewContainer of callStackView
is not destroyed for a swarm conference call because there are no
signals for call changes.This patch ensures chatViewContainer is used
when there is no call.
GitLab: #1625
Change-Id: Iefc39b747d92543244d30aa987eda134ff0a03f3
The function which is responsible for muting the camera when accepting
a call in audio assumes that the call's mediaList has already been
initialized, but this wasn't actually the case. This caused a bug where
the 'Accept in audio' button behaved exactly like the 'Accept in video'
button.
GitLab: #1621
Change-Id: I26251f51862cf5cd9b6d4daaf15270943c0e3c4e
With Jami-Daemon >= 14.0.0, the client doesn't need to construct
itself the history. This part is now handled by the daemon.
This patch uses the new API:
+ loadConversationMessages->loadConversation
+ SwarmMessageReceived/SwarmMessageUpdated/ReactionAdded/ReactionRemoved
+ remove MessageReceived
+ ConversationLoaded->SwarmLoaded
+ No need to use loadConversationUntil, the daemon will load whatever
the client needs.
+ No need to clear cache, just reset the body and emit data changes
Everything should work like before (even re-translation & changing
preview preference)
Change-Id: Iaf1fa3e84e8e157ae2d0bec210977f9a34415ebc
When adding/removing a file sharing we must add/remove
not only the video but also the audio media attributes
to the media change proposal.
GitLab: https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/485
Change-Id: Ifa6be8d500a43b1c2494501a4d6a6a6f009fdb62
There was no way to differentiate a 1:1 incoming call and a call
from a swarm, because username couldn't be checked. Now, create
conversation only if it's a 1:1 call
Change-Id: I0094967914b4888d083b9adc1d2b11de467d6f48
It works with a Pimpl which the right pttlistener.cpp depending
on the platform you are on (macOs, windows or X11). It is a
global PTT which listen to key events during calls. If the
global PTT is not supported, a local PTT is set.
https://git.jami.net/savoirfairelinux/jami-project/-/issues/1402
Change-Id: I8399800966c737bb8e8a656ecbb6af7ac7cdde8c
To be able to show calls that are transfered, we must catch new calls
from callstatechanged signal. Move all logic from newincomingcall to
callstatechanged.
Change-Id: Ibd3ff5f8b4009895b3165348fd1638956f5f66d9
Not useful in calladapter as we need to check if it's for the current
call. Also, fix some race-confitions where the callparticipantsmodel
was empty (in swarm-call with only the host in general)
https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/639
Change-Id: I69df1aa9f7d2d5b198c0fdc01e88e36f9c2c0bd7
If a call starts in a swarm, the host must show the confId.
The current call wasn't updated when a call is upgraded to a conference
causing the wrong call to be shown due to the new logic
Change-Id: I990d39e6e04253bc087fd0ec73c5b6c7906f93d9
Introduces the ViewCoordinator component to promote dynamic view loading and reduce coupling between components.
The following objects are now created and destroyed as needed:
- SettingsView
- WizardView
- dialogs
Further refactoring will be required in order to do the same with the ConversationView, which now parents the ChatView and the CallStackView.
Gitlab: #897
Change-Id: Ice6a0c133e62e1e0c8d7fb99ec2c41234c049b59
If a user join a conference with video enabled, but without any
valid camera and try to un-mute/mute in loop, it will add
new empty medias with incorrect sources causing duplicated participants
in the conference.
Change-Id: Ifa0dc090ca49ae6f9799f1209f3514cf540365da
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 a notification in the conversation like Anroid when the account
is disabled or when there is no network connectivity
Change-Id: I0f875fd24a2b29b8f7f48746651b156451e1250f
+ 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
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
Starting from audio only call:
- start sharing;
- add camera;
- stop sharing;
The camera stream should remain and not the sharing one.
Change-Id: If6dd0fb7a6ddd8603626c66c792e75e3cf05275e
The only missing case were for changing the current default camera.
Other methods can be removed.
Change-Id: I91fce779f4a41fe4d667444aea57b1b454aa702b
GitLab: #651
