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). --- src/tests/test-sms-part.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/tests') diff --git a/src/tests/test-sms-part.c b/src/tests/test-sms-part.c index 7d03f8f6..6a3f7183 100644 --- a/src/tests/test-sms-part.c +++ b/src/tests/test-sms-part.c @@ -536,7 +536,7 @@ common_test_create_pdu (const gchar *smsc, mm_sms_part_set_encoding (part, encoding); } if (validity > 0) - mm_sms_part_set_validity (part, validity); + mm_sms_part_set_validity_relative (part, validity); if (class > 0) mm_sms_part_set_class (part, class); -- cgit v1.2.3-70-g09d2