From f9105bff875ae0e7263718a317e156948957a6d0 Mon Sep 17 00:00:00 2001 From: Aleksander Morgado Date: Wed, 3 Apr 2013 16:30:48 +0200 Subject: 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). --- docs/reference/api/ModemManager-sections.txt | 1 + 1 file changed, 1 insertion(+) (limited to 'docs/reference/api') 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
-- cgit v1.2.3-70-g09d2