Accessing smartlist on conversationRemoved can return invalid
items. Instead, only show welcome view and use modelChanged signal
for updating smartlist.
Also avoid duplicate navigation to welcome view.
Gitlab: #300
Change-Id: Ic1c192fecceeb59287267e3445fabf6afb91ffd5
- avoid using smartlist index change for conversation selection
when call ends (instead it can be triggered from calladapter)
- break long lines
Gitlab: #260
Change-Id: Iaa1f9269d9ba6889fb1a7e466cd586fa86263bc7
Note: if the Displayname/alias is the same as the username,
it should be the only line shown
Gitlab: #129
Change-Id: I2c3dc8d304bd730a2ae114e4686c9ae899087c6b
- 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
1. When there is no contact, some properties in smart list view could be null
2. When creating new accounts from no accounts, adding a new contact and
switch accounts will cause "Contact out of range". This is caused by
smartlist model account id does not update at that time. Instead,
use current account id always.
Change-Id: Ic42ec33c4932908caff2ebca2814903f95c12a10
- 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
The clientwrapper class masks granular object registration within
qml, and encourages code duplication between viewmodels(adapters)
and code lasagnafication and the misuse of declarative Qml.
Change-Id: I85fef214363e62e54fc0681282323ea4861000d6
Gitlab: #66
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
- 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
