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
Yeah, it's a bug. Since you're doing CreateMessage call from VM constructor, the message container in the view isn't yet bound to the manager.
NotificationMessageContainer only listens for OnMessageQueued and that's not triggered when you give it a manager with message already in queue.
Here after attaching event handlers, ManagerOnOnMessageDismissed should be called for all existing messages and ManagerOnOnMessageQueued for each message from the new manager.
Could this be it? Can you test this by not calling CreateMessage from constructor but for example on view Loaded?
The text was updated successfully, but these errors were encountered:
AleksandarDev
changed the title
NotificationMessageContainer not initializing with existing messages when context changes
NotificationMessageContainer not initializing with existing messages when new context is set
May 29, 2018
Reported in #14
Yeah, it's a bug. Since you're doing CreateMessage call from VM constructor, the message container in the view isn't yet bound to the manager.
NotificationMessageContainer only listens for OnMessageQueued and that's not triggered when you give it a manager with message already in queue.
Here after attaching event handlers, ManagerOnOnMessageDismissed should be called for all existing messages and ManagerOnOnMessageQueued for each message from the new manager.
Could this be it? Can you test this by not calling CreateMessage from constructor but for example on view Loaded?
The text was updated successfully, but these errors were encountered: