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

Change the information about the timeout. If the timeout is 0, it's up to the server to determine what to do (which should be urgency and type-specific)

This commit is contained in:
Christian Hammond 2004-06-30 18:58:41 +00:00
parent 25e119c21b
commit a52bde5491
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
SPECIFICATION
View File

@ -26,7 +26,7 @@ Example use cases include:
* Presence changes in IM programs: for instance, MSN Messenger on * Presence changes in IM programs: for instance, MSN Messenger on
Windows pioneered the use of passive popups to indicate presence Windows pioneered the use of passive popups to indicate presence
changes. changes.
* New mail notification * New mail notification
* Low disk space/battery warnings * Low disk space/battery warnings
@ -48,7 +48,7 @@ by the bus process, however this is not required and notification
server clients must not assume that it is available. server clients must not assume that it is available.
The server should implement the "org.freedesktop.Notifications" interface on The server should implement the "org.freedesktop.Notifications" interface on
an object with the path "/org/freedesktop/Notifications". This is the an object with the path "/org/freedesktop/Notifications". This is the
only interface required by this version of the specification. only interface required by this version of the specification.
A notification has the following components: A notification has the following components:
@ -75,12 +75,13 @@ A notification has the following components:
- A timeout: the time in milliseconds after which the notification - A timeout: the time in milliseconds after which the notification
should be hidden (FIXME: should this be a function of text length should be hidden (FIXME: should this be a function of text length
to accommodate different reading speeds?). If zero the notification to accommodate different reading speeds?). If zero, the notification's
stays on-screen indefinitely (persistent notifications). timeout is dependent on the notification server's settings, and may vary
for the type of notification.
The timeout should be respected by implementations, but this is not The timeout should be respected by implementations, but this is not
required (this is for compatibility with KNotify). 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 (FIXME: should this be unique within a session, or just unique while