-
Notifications
You must be signed in to change notification settings - Fork 493
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
Toast notifications on WasabiWindow #845
Comments
Concept ACK. |
I will be working on a proposal for this. |
Probably this is not 100% related to the ticket but I think it would be good to handle all the notifications, alerts, error messages in an uniform way. Currently we each functionality display messages in a different place. We could add a notifications bar on top of the status bar and display errors and messages there. It doesn't use more UI space because i reduced the margins and spacing. What do you think? |
I think it's 100% related and it's a good idea. But with Toast Notifications implemented it makes no sense. Now the question is should we drop Toast Notifications plan in favor of this altogether or not? I would vote for Toast, but I can be convinced otherwise. @danwalmsley @molnard @lontivero Make your vote. |
I think it is good enough for now it look much better than the randomly placed texts. Also the code will be cleaner with this. If @lontivero implements this with a uniform interface than later we can change the graphical part to a better one.
|
My vote is to have this until we get toast notifications (provided its not a lot of work) Otherwise why not put the effort into toast notifications. If we do this, we could make the ui a control that overlays and looks like a toast notification. |
Temporary messages like:
are now appearing among the controls of the Wallet UI. This could be replaced with toast notifications which is already used by different platforms. Usually these notifications are showed at the center bottom of the window and disappearing after a few seconds.
The text was updated successfully, but these errors were encountered: