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