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). --- libmm-glib/mm-sms.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'libmm-glib/mm-sms.h') diff --git a/libmm-glib/mm-sms.h b/libmm-glib/mm-sms.h index 6cfb5b78..cb5b2b9d 100644 --- a/libmm-glib/mm-sms.h +++ b/libmm-glib/mm-sms.h @@ -86,7 +86,8 @@ gchar *mm_sms_dup_timestamp (MMSms *self); const gchar *mm_sms_get_discharge_timestamp (MMSms *self); gchar *mm_sms_dup_discharge_timestamp (MMSms *self); -guint mm_sms_get_validity (MMSms *self); +MMSmsValidityType mm_sms_get_validity_type (MMSms *self); +guint mm_sms_get_validity_relative (MMSms *self); guint mm_sms_get_class (MMSms *self); -- cgit v1.2.3-70-g09d2