NAME<\/a> ______________________________________________________________________________<\/p>\n dde \u2212 Execute a Dynamic Data Exchange command<\/p>\n package require dde 1.4<\/b><\/p>\n dde servername<\/b> ?\u2212force<\/b>? ?\u2212handler<\/b> proc<\/i>? ?\u2212\u2212<\/b>? ?topic<\/i>?<\/p>\n dde execute<\/b> ?\u2212async<\/b>? ?\u2212binary<\/b>? service topic data<\/i> \u2502<\/big><\/p>\n dde poke<\/b> ?\u2212binary<\/b>? service topic item data<\/i><\/p>\n dde request<\/b> ?\u2212binary<\/b>? service topic item<\/i><\/p>\n dde services<\/b> service topic<\/i><\/p>\n dde eval<\/b> ?\u2212async<\/b>? topic cmd<\/i> ?arg arg …<\/i>? ______________________________________________________________________________<\/p>\n This command allows an application to send Dynamic Data Exchange (DDE) command when running under Microsoft Windows. Dynamic Data Exchange is a mechanism where applications can exchange raw data. Each DDE transaction needs a service name<\/i> and a topic<\/i>. Both the service name<\/i> and topic<\/i> are application defined; Tcl uses the service name TclEval<\/b>, while the topic name is the name of the interpreter given by dde servername<\/b>. Other applications have their own service names<\/i> and topics<\/i>. For instance, Microsoft Excel has the service name Excel<\/b>.<\/p>\n The following commands are a subset of the full Dynamic Data Exchange set of commands. dde servername<\/b> registers the interpreter as a DDE server with the service name TclEval<\/b> and the topic name specified by topic<\/i>. If no topic<\/i> is given, dde servername<\/b> returns the name of the current topic or the empty string if it is not registered as a service. If the given topic<\/i> name is already in use, then a suffix of the form \u201c #2\u201d or \u201c #3\u201d is appended to the name to make it unique. The command\u2019s result will be the name actually used. The \u2212force<\/b> option is used to force registration of precisely the given topic<\/i> name.<\/p>\n The \u2212handler<\/b> option specifies a Tcl procedure that will be called to process calls to the dde server. If the package has been loaded into a safe interpreter then a \u2212handler<\/b> procedure must be defined. The procedure is called with all the arguments provided by the remote call.<\/p>\n dde execute<\/b> ?\u2212async<\/b>? ?\u2212binary<\/b>? service topic data<\/i><\/p>\n dde execute<\/b> takes the data<\/i> and sends it to the server indicated by service<\/i> with the topic indicated by topic<\/i>. Typically, service<\/i> is the name of an application, and topic<\/i> is a file to work on. The data<\/i> field is given to the remote application. Typically, the application treats the data<\/i> field as a script, and the script is run in the application. The \u2212async<\/b> option requests asynchronous invocation. The command returns an error message if the script did not run, unless the \u2212async<\/b> flag was used, in which case the command returns immediately with no error. \u2502<\/big> Without the \u2212binary<\/b> option all data will be sent in unicode. For \u2502<\/big> dde clients which don\u2019t implement the CF_UNICODE clipboard \u2502<\/big> format, this will automatically be translated to the system \u2502<\/big> encoding. You can use the \u2212binary<\/b> option in combination with the \u2502<\/big> result of encoding convertto<\/b> to send data in any other encoding.<\/p>\n dde poke<\/b> ?\u2212binary<\/b>? service topic item data<\/i><\/p>\n dde poke<\/b> passes the data<\/i> to the server indicated by service<\/i> using the topic<\/i> and item<\/i> specified. Typically, service<\/i> is the name of an application. topic<\/i> is application specific but can be a command to the server or the name of a file to work on. The item<\/i> is also application specific and is often not used, but it must always be non-null. The data<\/i> field is given to the remote application. Without the \u2212binary<\/b> option all data will be \u2502<\/big> sent in unicode. For dde clients which don\u2019t implement the \u2502<\/big> CF_UNICODE clipboard format, this will automatically be \u2502<\/big> translated to the system encoding. You can use the \u2212binary<\/b> \u2502<\/big> option in combination with the result of encoding convertto<\/b> to \u2502<\/big> send data in any other encoding.<\/p>\n dde request<\/b> ?\u2212binary<\/b>? service topic item<\/i><\/p>\n dde request<\/b> is typically used to get the value of something; the value of a cell in Microsoft Excel or the text of a selection in Microsoft Word. service<\/i> is typically the name of an application, topic<\/i> is typically the name of the file, and item<\/i> is application-specific. The command returns the value of item<\/i> as defined in the application. Normally this is interpreted to be a string with terminating null. If \u2212binary<\/b> is specified, the result is returned as a byte array.<\/p>\n dde services<\/b> service topic<\/i><\/p>\n dde services<\/b> returns a list of service-topic pairs that currently exist on the machine. If service<\/i> and topic<\/i> are both empty strings ({}), then all service-topic pairs currently available on the system are returned. If service<\/i> is empty and topic<\/i> is not, then all services with the specified topic are returned. If service<\/i> is non-empty and topic<\/i> is, all topics for a given service are returned. If both are non-empty, if that service-topic pair currently exists, it is returned; otherwise, an empty string is returned.<\/p>\n dde eval<\/b> ?\u2212async<\/b>? topic cmd<\/i> ?arg arg …<\/i>?<\/p>\n dde eval<\/b> evaluates a command and its arguments using the interpreter specified by topic<\/i>. The DDE service must be the TclEval<\/b> service. The \u2212async<\/b> option requests asynchronous invocation. The command returns an error message if the script did not run, unless the \u2212async<\/b> flag was used, in which case the command returns immediately with no error. This command can be used to replace send on Windows.<\/p>\n A Tcl interpreter always has a service name of TclEval<\/b>. Each different interpreter of all running Tcl applications must be given a unique name specified by dde servername<\/b>. Each interp is available as a DDE topic only if the dde servername<\/b> command was used to set the name of the topic for each interp. So a dde services TclEval {}<\/b> command will return a list of service-topic pairs, where each of the currently running interps will be a topic.<\/p>\n When Tcl processes a dde execute<\/b> command, the data for the execute is run as a script in the interp named by the topic of the dde execute<\/b> command.<\/p>\n When Tcl processes a dde request<\/b> command, it returns the value of the variable given in the dde command in the context of the interp named by the dde topic. Tcl reserves the variable $TCLEVAL$EXECUTE$RESULT<\/b> for internal use, and dde request<\/b> commands for that variable will give unpredictable results.<\/p>\n An external application which wishes to run a script in Tcl should have that script store its result in a variable, run the dde execute<\/b> command, and then run dde request<\/b> to get the value of the variable.<\/p>\n When using DDE, be careful to ensure that the event queue is flushed using either update<\/b> or vwait<\/b>. This happens by default when using wish<\/b> unless a blocking command is called (such as exec<\/b> without adding the &<\/b> to place the process in the background). If for any reason the event queue is not flushed, DDE commands may hang until the event queue is flushed. This can create a deadlock situation.<\/p>\n This asks Internet Explorer (which must already be running) to go to a particularly important website:<\/p>\n package require dde tk(n), winfo(n), send(n)<\/p>\n application, dde, name, remote execution<\/p>\n dde \u2212 Execute a Dynamic Data Exchange command <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3783,1],"tags":[2941,2635],"class_list":["post-6360","post","type-post","status-publish","format-standard","hentry","category-n-comandos-tcl-tk","category-sin-categoria","tag-dde","tag-mann"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6360","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=6360"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6360\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=6360"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=6360"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=6360"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
SYNOPSIS<\/a>
DESCRIPTION<\/a>
DDE COMMANDS<\/a>
DDE AND TCL<\/a>
EXAMPLE<\/a>
SEE ALSO<\/a>
KEYWORDS<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
DDE COMMANDS <\/a> <\/h2>\n
dde servername<\/b> ?\u2212force<\/b>? ?\u2212handler<\/b> proc<\/i>? ?\u2212\u2212<\/b>? ?topic<\/i>?<\/p>\nDDE AND TCL <\/a> <\/h2>\n
EXAMPLE <\/a> <\/h2>\n
dde execute<\/b> -async iexplore WWW_OpenURL http:\/\/www.tcl.tk\/<\/p>\nSEE ALSO <\/a> <\/h2>\n
KEYWORDS <\/a> <\/h2>\n
\n","protected":false},"excerpt":{"rendered":"