colin/ModemManager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

api,introspection: update 'Validity' property in the SMS interface

Browse Source 
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).
This commit is contained in:
Aleksander Morgado
2013-04-03 16:30:48 +02:00
parent 372a49bbf6
commit f9105bff87
11 changed files with 147 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
include/ModemManager-enums.h
View File

@@ -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.