|
|
|
ttdt_Get_Modified(3) -- ask if any ToolTalk client has changes pending on a file
|
|
The ttdt_Get_Modified function sends a Get_Modified request in the scope the_scope and waits for the reply. A Get_Modified request asks if any ToolTalk client has changes pending on pathname that it intends to make persistent. The context argument describes the environment to use. If context is not zero, messages created by ttdt_Get_Modified inherit from context all contexts whose slotname begins ... |
|
ttdt_message_accept(3) -- accept a contract to handle a ToolTalk request
|
|
The ttdt_message_accept function registers in the default session for TT_HANDLER-addressed requests: 1. Get_Geometry, Set_Geometry, Get_Iconified, Set_Iconified, Get_Mapped, Set_Mapped, Raise, Lower, Get_XInfo 2. Pause, Resume 3. Quit, Get_Status If the shell argument is not NULL, the ToolTalk service handles messages in (1) transparently; otherwise, it treats them like messages in (3). If shell i... |
|
|
ttdt_open(3) -- create a ToolTalk communication endpoint
|
|
The ttdt_open function calls tt_open(3) and tt_fd(3). It associates toolname, vendor and version with the created procid, and initializes the new procid's default contexts from the process environment. If sendStarted is True, ttdt_open sends a Started notice. |
|
ttdt_Revert(3) -- request a ToolTalk client to revert a file
|
|
The ttdt_Revert function sends a Revert request in the the_scope argument and waits for the reply. A Revert request asks the handling ToolTalk client to discard any changes pending on pathname. The context argument describes the environment to use. If context is not zero, messages created by ttdt_Revert inherit from context all contexts whose slotname begins with the characters ENV_. The the_scope... |
|
ttdt_Save(3) -- request a ToolTalk client to save a file
|
|
The ttdt_Save function sends a Save request in the the_scope argument and waits for the reply. A Save request asks the handling ToolTalk client to save any changes pending on pathname. The context argument describes the environment to use. If context is not zero, messages created by ttdt_Save inherit from context all contexts whose slotname begins with the characters ENV_. The the_scope argument i... |
|
ttdt_sender_imprint_on(3) -- act like a child of the specified tool
|
|
The ttdt_sender_imprint_on function is used to make the calling tool act equivalently to a child of another specified tool. The calling tool adopts the other tool's X11 display, locale, and current working directory. It also learns the other tool's X11 geometry, so that it may position itself appropriately. If the handler argument is non- NULL, the requests are addressed to that procid using TT_... |
|
ttdt_session_join(3) -- join a ToolTalk session
|
|
The ttdt_session_join function joins the session sessid, registering patterns and default callbacks for many standard Desktop message interfaces. If sessid is NULL, the default session is joined. The ttdt_session_join function registers for the following TT_HANDLER-addressed requests: 1. Get_Environment, Set_Environment, Get_Locale, Set_Locale, Get_Situation, Set_Situation, Signal, Get_Sysinfo 2. ... |
|
ttdt_session_quit(3) -- quit a ToolTalk session
|
|
The ttdt_session_quit function destroys the patterns in sess_pats. If quit is True, it quits the session sessid, or the default session if sessid is NULL. |
|
ttdt_subcontract_manage(3) -- manage an outstanding request
|
|
The ttdt_subcontract_manage function allows a requester to manage the standard Desktop interactions with the tool that is handling the request. The ttdt_subcontract_manage function registers in the default session for TT_HANDLER-addressed requests Get_Geometry and Get_XInfo, and Status notices. If shell is not NULL, the ToolTalk service handles the Get_Geometry and Get_XInfo notices transparently;... |
|
ttmedia_Deposit(3) -- send a Deposit request to checkpoint a document
|
|
The ttmedia_Deposit function is used to perform a checkpoint save on a document that was the subject of a Media Exchange load_contract request such as Edit, Compose, or Open. To carry out a checkpoint save, the editor must send the new document contents back to the sender of load_contract. The ttmedia_Deposit function creates and sends a Deposit request and returns the success or failure of that r... |
|
ttmedia_load(3) -- send a Display, Edit or Compose request
|
|
The ttmedia_load function is used to create and optionally send a Media Exchange request to display, edit or compose a document. The cb argument will be passed clientdata when the reply is received, or when intermediate versions of the document are checkpointed through Deposit requests. The op argument must be one of TTME_DISPLAY, TTME_EDIT or TTME_COMPOSE. The media_type argument names the data f... |
|
ttmedia_load_reply(3) -- reply to a Display, Edit or Compose request
|
|
The ttmedia_load_reply function is used to reply to a Media Exchange request to display, edit or compose a document. The editor working on the request usually calls ttmedia_load_reply when the user has indicated in some way that he or she is finished viewing or modifying the document. If new_contents and new_len are non- NULL and non-zero, respectively, ttmedia_load_reply uses their values to set ... |
|
ttmedia_ptype_declare(3) -- declare the ptype of a Media Exchange media editor
|
|
The ttmedia_ptype_declare function is used to initialize an editor that implements the Media Exchange message interface for a particular media type. The ttmedia_ptype_declare function notifies the ToolTalk service that the cb callback is to be called when the editor is asked to edit a document of the kind supported by ptype. The ttmedia_ptype_declare function installs an implementation-specific op... |
|
tttk_block_while(3) -- block while a counter is greater than zero
|
|
The tttk_block_while function is used to process asynchronous events, such as ToolTalk messages or window system events, while waiting for a condition or timeout. If app2run is not zero, then an event loop is run for that application context, by repeatedly calling XtAppProcessEvent(3) with ms_timeout being effected using XtAppAddTimeOut(3). If app2run is zero, then the file descriptor (as returned... |
|
tttk_message_abandon(3) -- finalize a message properly
|
|
The tttk_message_abandon function is used by an application when it does not understand a message and wants to get rid of it. The tttk_message_abandon function fails or rejects msg if appropriate, and then destroys it. The tttk_message_abandon will reject or fail the message only if msg is a TT_REQUEST in Tt_state TT_SENT. If it has a Tt_address of TT_HANDLER or a tt_message_status of TT_WRN_START... |
