diff options
| author | Christian Hammond <chipx86@chipx86.com> | 2005-07-28 18:25:25 +0000 |
|---|---|---|
| committer | Christian Hammond <chipx86@chipx86.com> | 2005-07-28 18:25:25 +0000 |
| commit | c0b423d9ecb9205f1e44a9713a7c15df5ab501e6 (patch) | |
| tree | 617c9815016bffa5b1276ab8c1fc8afa4394e35c | |
| parent | e09f9293735bd9548eedc9619c7b48922ba6b6a2 (diff) | |
| download | libnotify-c0b423d9ecb9205f1e44a9713a7c15df5ab501e6.tar.gz | |
Talk about variants as the dictionary values for hints.
| -rw-r--r-- | docs/ChangeLog | 7 | ||||
| -rw-r--r-- | docs/notification-spec.xml | 9 |
2 files changed, 15 insertions, 1 deletions
diff --git a/docs/ChangeLog b/docs/ChangeLog index 3027087..6a96326 100644 --- a/docs/ChangeLog +++ b/docs/ChangeLog @@ -1,3 +1,10 @@ +Mon Jul 25 22:48:54 PDT 2005 Christian Hammond <chipx86@gnupdate.org> + + * notification-spec.xml: + - Bump to version 0.7. + - Mention the x, y hints. + - Talk about variants as the dictionary values for hints. + Fri Apr 01 09:11:38 PST 2005 Christian Hammond <chipx86@gnupdate.org> * notification-spec.xml: diff --git a/docs/notification-spec.xml b/docs/notification-spec.xml index e187c14..ab92488 100644 --- a/docs/notification-spec.xml +++ b/docs/notification-spec.xml @@ -34,7 +34,7 @@ <date>28 July 2005</date> <authorinitials>cdh</authorinitials> <revremark> - Added "x" and "y" hints. + Added "x" and "y" hints. Talk about the variant type for hint values. </revremark> </revision> <revision> @@ -703,6 +703,13 @@ <literal>"x-<replaceable>vendor</replaceable>-<replaceable>name</replaceable>."</literal> </para> <para> + The value type for the hint dictionary in D-BUS is of the + <literal>DBUS_TYPE_VARIANT</literal> container type. This allows different + data types (string, integer, boolean, etc.) to be used for hints. When + adding a dictionary of hints, this type must be used, rather than putting + the actual hint value in as the dictionary value. + </para> + <para> The following table lists the standard hints as defined by this specification. Future hints may be proposed and added to this list over time. Once again, implementations are not required to support these. |