diff options
author | Aleksander Morgado <aleksander@lanedo.com> | 2013-04-03 16:30:48 +0200 |
---|---|---|
committer | Aleksander Morgado <aleksander@lanedo.com> | 2013-04-05 17:48:51 +0200 |
commit | f9105bff875ae0e7263718a317e156948957a6d0 (patch) | |
tree | 417299f51a7d17d7d5bd30692fd7b5ffd98092de /docs/reference/api | |
parent | 372a49bbf661c95110852c86df54008a7bad2774 (diff) |
api,introspection: update 'Validity' property in the SMS interface
We don't want to support only 'relative' validity, so don't assume that the
Validity property will always be a uint32 value.
Instead, we define the Validity propery as '(uv)' tuple, where the first value
(a MMSmsValidityType) specifies the type of validity, and the second value is
a variant formatted accordingly to what the validity type specifies (e.g. a
uint32 value if the type is MM_SMS_VALIDITY_TYPE_RELATIVE).
Diffstat (limited to 'docs/reference/api')
-rw-r--r-- | docs/reference/api/ModemManager-sections.txt | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/docs/reference/api/ModemManager-sections.txt b/docs/reference/api/ModemManager-sections.txt index 37309e9d..94cc0336 100644 --- a/docs/reference/api/ModemManager-sections.txt +++ b/docs/reference/api/ModemManager-sections.txt @@ -27,6 +27,7 @@ MMSmsPduType MMSmsState MMSmsDeliveryState MMSmsStorage +MMSmsValidityType </SECTION> <SECTION> |