Top |
DMS Write User Data responseDMS Write User Data response — Methods to manage the DMS Write User Data response. |
Collection of methods to create requests and parse responses of the DMS Write User Data message.
QmiMessageDmsWriteUserDataInput *
qmi_message_dms_write_user_data_input_new
(void
);
Allocates a new QmiMessageDmsWriteUserDataInput.
the newly created QmiMessageDmsWriteUserDataInput. The returned value should be freed with qmi_message_dms_write_user_data_input_unref()
.
Since: 1.0
QmiMessageDmsWriteUserDataInput *
qmi_message_dms_write_user_data_input_ref
(QmiMessageDmsWriteUserDataInput *self
);
Atomically increments the reference count of self
by one.
Since: 1.0
void
qmi_message_dms_write_user_data_input_unref
(QmiMessageDmsWriteUserDataInput *self
);
Atomically decrements the reference count of self
by one.
If the reference count drops to 0, self
is completely disposed.
Since: 1.0
gboolean qmi_message_dms_write_user_data_input_get_user_data (QmiMessageDmsWriteUserDataInput *self
,GArray **value_user_data
,GError **error
);
Get the 'User Data' field from self
.
Since: 1.0
gboolean qmi_message_dms_write_user_data_input_set_user_data (QmiMessageDmsWriteUserDataInput *self
,GArray *value_user_data
,GError **error
);
Set the 'User Data' field in the message.
self |
||
value_user_data |
a GArray of guint8 elements. A new reference to |
[in][element-type guint8][transfer none] |
error |
Return location for error or |
Since: 1.0
QmiMessageDmsWriteUserDataOutput *
qmi_message_dms_write_user_data_output_ref
(QmiMessageDmsWriteUserDataOutput *self
);
Atomically increments the reference count of self
by one.
Since: 1.0
void
qmi_message_dms_write_user_data_output_unref
(QmiMessageDmsWriteUserDataOutput *self
);
Atomically decrements the reference count of self
by one.
If the reference count drops to 0, self
is completely disposed.
Since: 1.0
gboolean qmi_message_dms_write_user_data_output_get_result (QmiMessageDmsWriteUserDataOutput *self
,GError **error
);
Get the result of the QMI operation.
Since: 1.0
QmiMessageDmsWriteUserDataOutput * qmi_message_dms_write_user_data_response_parse (QmiMessage *message
,GError **error
);
Parses a QmiMessage and builds a QmiMessageDmsWriteUserDataOutput out of it. The operation fails if the message is of the wrong type.
a QmiMessageDmsWriteUserDataOutput, or NULL
if error
is set. The returned value should be freed with qmi_message_dms_write_user_data_output_unref()
.
Since: 1.34
void qmi_client_dms_write_user_data (QmiClientDms *self
,QmiMessageDmsWriteUserDataInput *input
,guint timeout
,GCancellable *cancellable
,GAsyncReadyCallback callback
,gpointer user_data
);
Asynchronously sends a Write User Data request to the device.
When the operation is finished, callback
will be invoked in the thread-default main loop of the thread you are calling this method from.
You can then call qmi_client_dms_write_user_data_finish()
to get the result of the operation.
self |
a QmiClientDms. |
|
input |
||
timeout |
maximum time to wait for the method to complete, in seconds. |
|
cancellable |
a GCancellable or |
|
callback |
a GAsyncReadyCallback to call when the request is satisfied. |
|
user_data |
user data to pass to |
Since: 1.0
QmiMessageDmsWriteUserDataOutput * qmi_client_dms_write_user_data_finish (QmiClientDms *self
,GAsyncResult *res
,GError **error
);
Finishes an async operation started with qmi_client_dms_write_user_data()
.
self |
a QmiClientDms. |
|
res |
the GAsyncResult obtained from the GAsyncReadyCallback passed to |
|
error |
Return location for error or |
a QmiMessageDmsWriteUserDataOutput, or NULL
if error
is set. The returned value should be freed with qmi_message_dms_write_user_data_output_unref()
.
Since: 1.0
typedef struct _QmiMessageDmsWriteUserDataInput QmiMessageDmsWriteUserDataInput;
The QmiMessageDmsWriteUserDataInput structure contains private data and should only be accessed using the provided API.
Since: 1.0
typedef struct _QmiMessageDmsWriteUserDataOutput QmiMessageDmsWriteUserDataOutput;
The QmiMessageDmsWriteUserDataOutput structure contains private data and should only be accessed using the provided API.
Since: 1.0