aboutsummaryrefslogtreecommitdiff
path: root/introspection/org.freedesktop.ModemManager1.Sms.xml
AgeCommit message (Collapse)Author
2021-03-23api: add 'Since' tagsAleksander Morgado
These are not actively used by gdbus-codegen or gtk-doc, but they're helpful anyway so that users know when a given API method was introduced.
2019-08-29introspection: untabifyBen Chan
2018-06-09introspection: minor indentation fixes in SMS interfaceAleksander Morgado
2013-10-25api: add 'ServiceCategory' property to the SMS interfaceAleksander Morgado
Will be used in 3GPP2 SMS messages.
2013-10-25api: add 'TeleserviceId' property to the SMS interfaceAleksander Morgado
Will be used in 3GPP2 SMS messages.
2013-10-25api,introspection: minor indentation fixes in 'Validity' property definitionAleksander Morgado
2013-07-19api,introspection: update interface version numberAleksander Morgado
2013-06-11api,introspection: update copyright noticesAleksander Morgado
2013-05-06sms: add support for message classDan Williams
We need to redefine the message class property to int since class 0 is a valid message class. Thus -1 now means "unspecified class".
2013-04-05api,introspection: update 'Validity' property in the SMS interfaceAleksander Morgado
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).
2012-09-14sms: 'Text' and 'Data' will never be given at the same timeAleksander Morgado
When receiving an SMS, if the encoding is either GSM7 or UCS2, we will treat the contents of the SMS as text; and if the encoding is either 8BIT or unknown, we will just dump the contents of the SMS as data. When creating an SMS, the user is not allowed to give both text and data, only one can be given. We will use by default 8BIT when data is given, and guess the best encoding if text is given. Note that it's still possible to have SMS with neither text nor data, as in delivery status reports. This commit also handles the split of the input data in order to make it fit into singlepart or multipart messages.
2012-09-14api: new `DeliveryState' property in the SMS interfaceAleksander Morgado
Given only for STATUS REPORT SMS messages.
2012-09-14api: make read-only all SMS properties for nowAleksander Morgado
We don't support yet modifying these properties on the fly (e.g. we would need to re-construct the internal PDU list when the text changes).
2012-09-14api: new `MessageReference' property in the SMS interfaceAleksander Morgado
Message reference allows to match a sent SMS with its corresponding delivery report, if requested.
2012-09-14api: new `DischargeTimestamp' property for Status Report SMS messagesAleksander Morgado
2012-09-14api: new `PduType' property in the SMS interfaceAleksander Morgado
It will help deciding the type of message.
2012-09-14api: new `Sms.DeliveryReportRequest' propertyAleksander Morgado
Also allowing the 'delivery-report-request' key in the `Messaging.CreateSms()' method.
2012-09-14api: Sms.Store() now requires the specific memory storage where to store the SMSAleksander Morgado
... or MM_SMS_STORAGE_UNKNOWN to store it in the default storage.
2012-08-31api,introspection: new `Data' property in the SMS interfaceAleksander Morgado
We need to expose the raw data for the case where we get SMS messages with binary content (e.g. settings SMS).
2012-03-16introspection: setup all new files and remove old onesAleksander Morgado