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
I'm a new user of this library. Thanks a lot for this simple to use notification library for Windows !
I have a specific use case in my application where I want to raise a notification under certain conditions, but if theses conditions are no longer meet, I want to be able to clear the previous notification that was raised.
e.g.:
If connection to remote server cannot be established, then I raise a notification
..
When connection to remote server is restored, I want to clear the notification.
Looking at Windows API. Is seams to be possible to update or clear notification by defining tag and/or group.
My expectations
the function notify() should allow defining custom tag and custom group
a new function remove(tag, group) should be defined to clear notification identified by tag and group.
The text was updated successfully, but these errors were encountered:
Lets say my app is doing Step1, then it finished it so it showed user the toast (he did not close it).
Now user starts doing Step2, i want to clear all toasts.
Hello,
I'm a new user of this library. Thanks a lot for this simple to use notification library for Windows !
I have a specific use case in my application where I want to raise a notification under certain conditions, but if theses conditions are no longer meet, I want to be able to clear the previous notification that was raised.
e.g.:
If connection to remote server cannot be established, then I raise a notification
..
When connection to remote server is restored, I want to clear the notification.
Looking at Windows API. Is seams to be possible to update or clear notification by defining
tag
and/orgroup
.My expectations
notify()
should allow defining custom tag and custom groupremove(tag, group)
should be defined to clear notification identified by tag and group.The text was updated successfully, but these errors were encountered: