• Home
  • History
  • Annotate
  • Raw
  • Download
  • only in /barrelfish-2018-10-04/usr/eclipseclp/documents/embedding/

Lines Matching refs:control

87 thread-like control flow of the embedded interface. The
93 either the {\eclipse} side or the Tcl side has `control'. When the Tcl side
94 has control, execution of the {\eclipse} process is suspended. When the
95 {\eclipse} side has control, the Tcl side cannot initiate the execution of
96 ec_rpc goals. The interface can implicitly transfer control from one side
101 remote process is identified by a {\bf control} name, which is the
102 {\eclipse} name for a special control connection between the two sides.
177 end of the attachment, before control is handed over to the
178 {\eclipse} side (see section~\ref{remote-control} for more
191 such as the control connection and the connection to allow rpc goals to be
196 sides can then interact. Initially, the control is given to the Tcl side,
197 and {\it remote_connect/3} returns only when control is handed over to the
200 As part of the attachment process, the {\eclipse} name of the control
205 \item[\index{ec_control_name (Tcl remote interface)}{\bf ec_control_name}]\ \\ returns the {\eclipse} name of the control
280 {\bf ec_rpc} cannot be issued while {\eclipse} side has control.
326 achieved by transferring control between
345 not necessarily transfer control between {\eclipse} and
374 (see \bipref{set_event_handler/2}{../bips/kernel/event/set_event_handler-2.html}) is then executed when {\eclipse} has control.
453 {\eclipse} side initially has control and flushes
455 control is transferred to the Tcl
457 handler finishes, control is returned to the {\eclipse} side. The general
524 When the queue is flushed as shown above, then control is handed over to
567 producer. This handler is initiated when {\eclipse} side has control, and
569 handler defined, control is transferred to the Tcl side, where {\it
573 control is returned to the {\eclipse} side, and the read operation is
601 If the Tcl side has control, flushes the (synchronous or asynchronous) queue
603 control briefly to {\eclipse} to read the data. Control is
630 ec_flush} is invoked, control is actually transferred to {\eclipse}, and
632 returns control to Tcl to continue the execution of the handler. When the
633 handler finally finishes, control returns to {\eclipse}, and the original
646 {\eclipse}, {\eclipse} will print a warning and return control to Tcl side.
688 control will be handed over to Tcl, and {\bf ec_input_popup}
731 consumer. This handler is initiated when Tcl initially has control, and
734 consume the data. When the handler returns, control is returned to Tcl,
836 between {\eclipse} and Tcl sides without transfer of control.
849 Note that control is not handed over to Tcl side in this case:
851 invoked and executed on the Tcl side while {\eclipse} side still has control, with the
853 goals because {\eclipse} side still retains control. Another difference
875 control, and so there would not be an
877 would be invoked automatically on the {\eclipse} side, even when control is
884 the {\eclipse} side is given control.
896 With {\bf ec_flush}, control will be handed over to the
970 called, control is handed over to the Tcl to handle the data, and the
1005 control is {\it not\/} handed
1020 the command is invoked directly when Tcl side has control), then the
1049 is called when control is handed over to {\eclipse} side to read the
1089 the name of the control connection:
1098 The user specified name `myqueue' is appended to the control name of the
1106 % code fragment to remember the control name
1158 \label{remote-control}
1162 control between {\eclipse} and Tcl, and the disconnection of the Tcl
1192 For the transfer of control from Tcl to {\eclipse} and vice versa,
1195 side has the control (for example, the GUI may have a button that sends an
1197 call-back when control is transferred to {\eclipse} and reenabled when
1198 control is transferred back to Tcl).
1200 Note that there are two types of transfer of control from {\eclipse} to
1201 Tcl: 1) when the control is implicitly yielded (e.g.\ initiating I/O
1203 control is handed over by yielding explicitly (e.g.\ by calling
1205 expected to eventually handed back control implicitly to {\eclipse}, and
1206 not to explicitly hand control over to {\eclipse} before this. Thus two
1207 call-backs are provided when control is yield to Tcl: one is executed
1208 whenever the control is yielded, and the other is only executed when the
1209 control is explicitly yielded. Thus when control is explicitly yielded,
1212 explicitly transfer control back to {\eclipse} when pressed, which should
1216 disconnect. The event's name is the control stream's name. The user can
1225 checks if the {\eclipse} side has control. Returns 1 if {\eclipse}
1226 side has control, 0 otherwise. If that is the case,
1234 explicitly hand-over control to {\eclipse}. Tcl side must have
1235 control when this command is called (i.e. {\it ec_running\/} must
1237 control back to the Tcl side. Meanwhile, the Tcl process is not
1241 set up commands that will be called just before control is handed
1242 over to {\eclipse} ({\it start}), when control is handed back from
1243 {\eclipse} ({\it end}), when {\eclipse} explicitly yields control
1247 both when control change hands explicitly (e.g.\ via {\it
1277 Explicitly yields control from {\eclipse} to the remote side with
1278 the control stream {\it Control}. {\eclipse} execution will suspend
1279 until control is transferred back to {\eclipse}. This predicate
1280 returns when {\eclipse} side resumes control.
1307 :- remote_connect(localhost/5000, control,
1308 set_event_handler(control, disconnect_handler/0)),
1310 % Name for control connection is also fixed.
1317 % this is for yielding control to Tcl. No need to specify Control explicitly
1319 remote_yield(control).
1338 # disable the terminate button when control is transferred to ECLiPSe
1343 # enable the terminate button when control is transferred back to Tcl
1361 # disable button initially as ECLiPSe side has initial control
1367 # Tcl side initially has control, hand it over to ECLiPSe...
1387 button is disabled when {\eclipse} side has control, and this is done by
1408 within the Tcl/Tk GUI when control is transferred to {\eclipse}. Aside from