Using a custom getter setter cause the setting of the value to
require manual changed signal emission and in addition to being
error prone, this prevents the changed signal from being emitted
upon initial selection. Some excess workaround code may be removed
in following commits.
This patch also refactors the banned contact signaling as part of
an accountadapter connection cleanup.
Change-Id: I73fb751001e53e086adc7a6a8d706671c2878a77
When the needsSyncingSet signal is caught, we need to update the
UI to change filter tab, reload the conversation, etc.
Change-Id: I70170d75afa50acad6e79d53fcaeb82752c38e81
This should fix a race condition preventing the right conversation
from being selected after an outgoing interaction and, more rarely,
accepting an invitation.
Change-Id: Iccd1f91ba4d46285c2f1e4594122a736824b752f
1. Decline invites now auto-select the next one and de-select the
conversion when there are no more invites
2. Block conversations behaves the same as before
Gitlab: #402
Change-Id: Ibd3385e40cb2329d58ea90aa3347dfa4b66a4496
- use QString for interactionId
- swarm conversations: use loadConversationMessages and
subscribe to newMessagesAvailable signal
- avoid displaying "merge" and empty "data transfer" messages
- link composing status
Change-Id: Ic524bb786b2ff0471f03b1bb02d41d6da38e716a
Minor cosmetic changes to the account combo box, search bar, filter
tabs, and smartlist.
Change-Id: Ie8173504859b325374e42f0dbb4e0ae75f3ed740
Gitlab: #373
Gitlab: #374
Gitlab: #388
- Remove icons and resize side panel tab bar.
- Change icons and style for chatview header and combo box buttons.
- Update chatview colors.
Gitlab: #241
Change-Id: Ic5f4e0db5e1912c85cc4f658264371af8104cd8f
- switch tab to conversations smartlist
- go to welcomeview
TODO: define UI behavior while waiting for the smartlist update
Gitlab: #284
Change-Id: I251c49e5b0b418f41d5872ef09d32db5bc940df2
- switch between "conversations" - "invitations" smartlists according to call origin
- "Accept Request" button from msg's view header: hide on contact accepted, set on view load according to userType
- correct requests smartlist item selection on tab switch
- accept incoming call from pending contact makes conversation permanent
Gitlab: #74
Change-Id: Iadfef0d7e4032002d8007a4f18a9eae27f7ba230
- 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
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
By giving a base context menu, all context menus are generated at run time
and kept the same style. Some issues are fixed along with the patch.
Gitlab: #8
Gitlab: #35
Change-Id: Ieb812420fcb44c33d161a62c8574f6705dc5e1a9
- avoid duplicate call of LRC's setTopAccount()
- welcome view displays always the first account on the list, so passing the index is not necessary
- conversationsadapter and messagesadapter no longer listen to currentAccountChanged signal since there is a specific function for the setup
Gitlab: #12
Change-Id: Iac932d2596bf59c7528d83be799342ccefeea6b0
