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

5
SPECIFICATION
View File

@ -75,8 +75,9 @@ 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).