Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NotificationMessageContainer not initializing with existing messages when new context is set #15

Open
AleksandarDev opened this issue May 29, 2018 · 0 comments
Labels

Comments

@AleksandarDev
Copy link
Member

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?

@AleksandarDev 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant