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). --- include/ModemManager-enums.h | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'include/ModemManager-enums.h') diff --git a/include/ModemManager-enums.h b/include/ModemManager-enums.h index 6c121354..f297d1be 100644 --- a/include/ModemManager-enums.h +++ b/include/ModemManager-enums.h @@ -521,6 +521,22 @@ typedef enum { /*< underscore_name=mm_sms_storage >*/ MM_SMS_STORAGE_TA = 6, } MMSmsStorage; +/** + * MMSmsValidityType: + * @MM_SMS_VALIDITY_TYPE_UNKNOWN: Validity type unknown. + * @MM_SMS_VALIDITY_TYPE_RELATIVE: Relative validity. + * @MM_SMS_VALIDITY_TYPE_ABSOLUTE: Absolute validity. + * @MM_SMS_VALIDITY_TYPE_ENHANCED: Enhanced validity. + * + * Type of SMS validity value. + */ +typedef enum { /*< underscore_name=mm_sms_validity_type >*/ + MM_SMS_VALIDITY_TYPE_UNKNOWN = 0, + MM_SMS_VALIDITY_TYPE_RELATIVE = 1, + MM_SMS_VALIDITY_TYPE_ABSOLUTE = 2, + MM_SMS_VALIDITY_TYPE_ENHANCED = 3, +} MMSmsValidityType; + /** * MMModemLocationSource: * @MM_MODEM_LOCATION_SOURCE_NONE: None. -- cgit v1.2.3-70-g09d2