You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever user change the selected folder, the unreadMailCount message arrives from the cloud with info from that currently open folder, resulting in the notification dot and counter from the Windows application icons, to display misguiding information.
The unreadMailCount should follow two rules:
Should be the sum of unread emails in Inbox + user custom folders, regardless of what folder is currently open
Should keep informing unread mail count as described above, regardless of what folder the user has open.
(Edited to include user custom folders).
The text was updated successfully, but these errors were encountered:
Not sure I agree with that. The unread message badge should apply to all folders. Users, like me, may have rules routing messages to other folders for organizational purposes!
Not sure I agree with that. The unread message badge should apply to all folders. Users, like me, may have rules routing messages to other folders for organizational purposes!
You're correct, thats not what I meant, sorry for the confusion.
An example will be more clear I think: currently if you open Trash folder, the unread count message will be sent to the desktop app with the amount of unread emails in the Trash. Same for any folder.
So what we need is the unread count to be the sum of unread emails in Inbox, plus user custom folders, regardless of what folder is currently open. Sounds more like it? Will add this to the original message.
Whenever user change the selected folder, the unreadMailCount message arrives from the cloud with info from that currently open folder, resulting in the notification dot and counter from the Windows application icons, to display misguiding information.
The unreadMailCount should follow two rules:
(Edited to include user custom folders).
The text was updated successfully, but these errors were encountered: