jcarr
/
libnotify
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

We decided NIDs are unique within a session

This commit is contained in:
Mike Hearn 2004-07-06 20:48:50 +00:00
parent 075e6dda7f
commit 0ab190f75e
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
SPECIFICATION
View File

@ -90,13 +90,15 @@ A notification has the following components:
not required (this is for compatibility with KNotify). not required (this is for compatibility with KNotify).
Each notification displayed is allocated a unique ID by the server Each notification displayed is allocated a unique ID by the server.
(FIXME: should this be unique within a session, or just unique while This is unique within the session - while the notification server is
the notification is active?). This can be used to hide the running the ID will not be recycled unless the capacity of a uint32 is
notification before the expiration time is reached. It can also be used to exceeded.
atomically replace the notification with another: this allows you to
(for instance) modify the contents of a notification while it's This can be used to hide the notification before the expiration time
on-screen. is reached. It can also be used to atomically replace the notification
with another: this allows you to (for instance) modify the contents of
a notification while it's on-screen.
BACKWARDS COMPATIBILITY BACKWARDS COMPATIBILITY