The tt_message_create_super function creates a copy of the specified message and re-addresses the copy of the message to the parent of the otype contained within the message. The m argument is the opaque handle for the message involved in this operation.
The tt_message_destroy function destroys the message. Destroying a message has no effect on the delivery of a message already sent. The m argument is the opaque handle for the message involved in this operation.
The tt_message_disposition function retrieves the disposition attribute from the specified message. The m argument is the opaque handle for the message involved in this operation.
The tt_message_disposition_set function sets the disposition attribute for the specified message. The m argument is the opaque handle for the message involved in this operation. The r argument indicates whether an instance of the receiving process is to be started to receive the message immediately, or whether the message is to be queued until the receiving process is started at a later time. The ...
The tt_message_fail function informs the ToolTalk service that the process cannot handle the request just received. This function also informs the ToolTalk service that the message is not be offered to other processes of the same ptype. The ToolTalk service will send the message back to the sender with state TT_FAILED. The m argument is the opaque handle for the message involved in this operation.
The tt_message_file function retrieves the file attribute from the specified message. The m argument is the opaque handle for the message involved in this operation.
The tt_message_file_set function sets the file attribute for the specified message. The m argument is the opaque handle for the message involved in this operation. The file argument is the name of the file involved in this operation.
The tt_message_gid function retrieves the group identifier attribute from the specified message. The ToolTalk service automatically sets the group identifier of a message with the group identifier of the process that created the message. The m argument is the opaque handle for the message involved in this operation.
The tt_message_handler function retrieves the handler attribute from the specified message. The m argument is the opaque handle for the message involved in this operation.
The tt_message_handler_ptype function retrieves the handler ptype attribute from the specified message. The m argument is the opaque handle for the message involved in this operation.
The tt_message_handler_ptype_set function sets the handler ptype attribute for the specified message. The m argument is the opaque handle for the message involved in this operation. The ptid argument is the type of process that is to handle this message.
The tt_message_handler_set function sets the handler attribute for the specified message. The m argument is the opaque handle for the message involved in this operation. The procid argument is the character value that uniquely identifies the process that is to handle the message.
The tt_message_iarg_add function adds a new argument to a message object and sets the value to a given integer. Add all arguments before the message is sent. To change existing argument values, the application must use only modes TT_OUT or TT_INOUT. Adding arguments when replying to a message produces undefined results. The m argument is the opaque handle for the message involved in this operation...
The tt_message_icontext_set function sets the integer value of a message's context. This function overwrites any previous value associated with slotname. The m argument is the opaque handle for the message involved in this operation. The slotname argument describes the context of this message. The value argument is the integer value to be set.
The tt_message_id function retrieves the identifier of the specified message. The m argument is the opaque handle for the message involved in this operation.
