Lrc verifies if we should call refuse or hangup, so now we can unify the call ending function in client.
GitLab: #408
Change-Id: I35f7ca282c6e49e669d849a140772600e501711a
Minor cosmetic changes to the account combo box, search bar, filter
tabs, and smartlist.
Change-Id: Ie8173504859b325374e42f0dbb4e0ae75f3ed740
Gitlab: #373
Gitlab: #374
Gitlab: #388
- set UI according to sketch prototype
- add moderation overlay menu instead of context menu
- only update participants overlay when necessary
- avoid minimum size for ResponsiveImage
Gitlab: #207, #208
Change-Id: I65c9932319e55840518cbb0ce3cfa1a46e2275f0
- AccountAdapter::navigateToWelcomePageRequired is no longer required since subscription to property change in QML
- avoid unnecessary CallAdapter signals for UI management. Listen to BehaviorController and avoid duplicated / unnecessary signals.
- avoid duplicated code:
- account selection only in AccountAdapter::changeAccount and ConversationsAdapter::selectConversation
- simplification of ConversationsAdapter::selectConversation
- conversation UI always managed by ConversationsAdapter -> ConversationSmartListItemDelegate
- smartlistmodel: no need to show callstack for outgoing calls in state ENDED
Gitlab: #86
Gitlab: #87
Gitlab: #88
Change-Id: I7025d4292914939f5a78aee1c4742104b370641d
Make the difference between a host and a moderator. The main difference for
now is that the host can hang up calls, not the moderator because they don't
know the calls hosted
Change-Id: Iec36c4d26ae32126e8628bef6491c35d0228a45f
- Note: adds forcing the main window to the top to overcome a
Qt/QML bug which prevents this from working when activating
from a notification window source.
Change-Id: Ib5a93d3937fe5a4de0229f7aeae8469d1ffdfba3
- incoming / outgoing call UI management
- add system native notifications
- incoming call page same model as outgoing
- UserInfoCallPage is used to display common information for incoming / outgoing calls
Gitlab: #32
Change-Id: If33196a30c51698b4edad55cb8f718066034e422
It seems concurrent calls to invokeMethod using qml component
object pointers can lead to access violations. These method
invocations can be replaced with a signal/slot mechanism.
This patch replaces only the invocations in conversationsadapter
and accountsadapter that are known to be problematic for now.
Some code cleanup is done for QmlAdapterBase derived classes.
Gitlab: #61
Change-Id: I72f47c9229a9bf42299ae52822c3a1a8c04eb423
In order to make it work with the translations, call status is no longer passed as a string but as an integer (from enum lrc::api::call::Status).
Gitlab: #10
Change-Id: If8d8b7093fbf82e9b7732e6991eec647ad0d50b7
