summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Hearn <mike@navi.cx>2004-07-29 21:02:55 +0000
committerMike Hearn <mike@navi.cx>2004-07-29 21:02:55 +0000
commitf26e56113a3cf80729977fcedd77b93a490b2e3e (patch)
treee42077629a6509816044bd23e08097b6ccb86603
parent392d030acfb438b8adcf1d0fbe54dcbd8369294f (diff)
downloadlibnotify-f26e56113a3cf80729977fcedd77b93a490b2e3e.tar.gz
First attempt at wording for default actions
-rw-r--r--SPECIFICATION23
1 files changed, 14 insertions, 9 deletions
diff --git a/SPECIFICATION b/SPECIFICATION
index 9a3ca42..8c2f2f0 100644
--- a/SPECIFICATION
+++ b/SPECIFICATION
@@ -270,7 +270,7 @@ The following messages must be supported by all implementations.
* GetServerInformation
- This message takes no parameters, and returns the following values:
+ This message takes no parameters, and returns the following values in an array:
STRING name: the product name of the server
STRING vendor: "kde"/"freedesktop.org"/"Microsoft" etc etc
@@ -296,19 +296,24 @@ All implementations must emit the following signals:
The following signals MAY be emitted by the server.
-* ActionInvoked
+* Invoked
- If the server specifies "actions" in its caps array, and actions
- were specified in the original request, this signal must be emitted
- if the user invokes a given action (for instance, by clicking a
- button).
+ This signal is emitted when:
+
+ - The user performs some global "invoking" action upon a notification,
+ for instance by clicking on its graphical representation
+ - The user invokes a specific action as specified in the original
+ Notify request, for example by clicking on the action button.
ActionInvoked has two parameters:
* UINT32 id: The ID of the notification containing the invoked action.
- * UINT32 action_id: The ID of the action that was invoked, which was
- specified in the original dictionary.
-
+ * UINT32 action_id: Zero means the default invoke action that can be
+ performed on any notification. 1+ is the index in
+ the actions array originally specified.
+ Clients should not assume the server will generate this signal: some
+ servers may not support user interaction at all, or may not support
+ the concept of being able to "invoke" a notification.