We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to the spec:
If replaces_id is not 0, the returned value is the same value as replaces_id.
replaces_id
However, linux_notification_center assigns a new ID even when replacing a notification.
linux_notification_center
This can e.g. by reproduced by doing:
$ gdbus call --session \ --dest org.freedesktop.Notifications \ --object-path /org/freedesktop/Notifications \ --method org.freedesktop.Notifications.Notify \ -- \ my_app_name \ 0 \ gtk-dialog-info \ "The Summary" \ "Here's the body of the notification" \ '[]' \ '{}' \ -1 (uint32 32,)
then with the ID from above:
$ gdbus call --session \ --dest org.freedesktop.Notifications \ --object-path /org/freedesktop/Notifications \ --method org.freedesktop.Notifications.Notify \ -- \ my_app_name \ 32 \ gtk-dialog-info \ "The Summary 2" \ "Here's the body of the notification" \ '[]' \ '{}' \ -1 (uint32 33,)
replacing itself works fine (not sure anymore about this!), but there's a new ID returned.
The text was updated successfully, but these errors were encountered:
notifications: Add quirks for deadd
122b189
phuhl/linux_notification_center#160 phuhl/linux_notification_center#161
c65d6b2
No branches or pull requests
According to the spec:
However,
linux_notification_center
assigns a new ID even when replacing a notification.This can e.g. by reproduced by doing:
then with the ID from above:
replacing itself works fine(not sure anymore about this!), but there's a new ID returned.The text was updated successfully, but these errors were encountered: