Address-based account color is used until own key is created/imported #7296
Description
When an account is configured, it doesn't have own key yet, a message should be sent or the "QR INVITE CODE" window opened, or a key imported e.g. from ASM, so that key::store_self_keypair() is called. Before that the account color is computed from the configured address. Steps to reproduce:
- Take DC Desktop.
- Create a new account. It already has color on the side panel, but it's wrong.
- Open the "QR INVITE CODE" window, see that the actual account color is different.
- Restart the app. Now the color on the side panel is correct too.
Suggested fix:
- Use our favorite gray color until the self-key is available. This will be consistent with a gray avatar placeholder (with "?" inside) on the side panel when a new account is being created.
- Emit
AccountsChanged(as @Simon-Laux suggested in fix: Emit AccountsItemChanged when own key is generated/imported, use gray self-color until that (#7296) #7291 (comment)) when the self-key is available so that UIs can update the color. Or betterAccountsItemChanged.