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

fix: multi-message notification causing application to become unresponsive #69

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

muwoo
Copy link
Contributor

@muwoo muwoo commented Aug 5, 2024

#68 When there is a new message notification, the historical message will be automatically closed.

muwoo added 2 commits August 5, 2024 12:15
When there is a new message notification, the historical message will be automatically closed.
add change file
@muwoo muwoo changed the title fix: #68 fix: multi-message notification causing application to become unresponsive Aug 5, 2024
@FabianLars FabianLars requested a review from amrbashir August 5, 2024 08:19
Copy link
Member

@amrbashir amrbashir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like this PR removed the notification stacking and only shows one notification at a time, this is not desired at all.

@muwoo
Copy link
Contributor Author

muwoo commented Aug 21, 2024

@amrbashir Thank you for your reply, but I have a question to ask. The message notification interaction of Windows 10 and MacOS is to remove the historical message notifications after the new message notifications are displayed. Why doesn't Windows 7 keep the same mode and use the stacking mode?

@amrbashir
Copy link
Member

The idea is to give the user a chance to see the notification because there is no notification center in Windows 7 and once it is closed, there is no way for them to see it ever again.

Windows 10 & 11, they have a different behavior indeed but they save notifications in a queue and show them one by one, I am fine with implementing that instead if possible but the current PR removes the previous notification immediately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants