| Prev | Next | Basic Verbs > DDEEvent |
DDEEvent
| Syntax |
DDEEvent (appID, verbID, transactionID [, key1, value1 [, keyN, valueN]...]
|
| Params |
appID is a value identifying the application to which this verb is addressed. It can be a string4 containing the application signature, a binary value obtained by calling sys.browseNetwork or a string containing a valid network address. verbID is a string4 indicating the Apple event verb ID. transactionID is a number identifying the transaction of which this verb is a part. key1 is a string4 indicating the keyword for the first parameter value. value1 is the first parameter value, and can by any type. [keyN, valueN] are additional keyword and parameter value pairs.
|
| Action |
Sends an Apple event with the verb class 'DDE ' and with the specified verbID and transactionID to the application identified by appID, including one parameter for each keyN, valueN pair provided, and returns immediately, not waiting for a reply.
|
| Returns |
True
|
| Examples |
For examples of the use of DDEEvent, see the scripts in the system.verbs.apps.DDE table. |
| Errors |
If the application indicated by appID is not running, or doesn't know how to handle the given verb, an error will occur.
|
| Notes |
This is a very advanced Frontier verb of primary interest to implementers and advanced scripters. It is not necessary to understand it to use Frontier effectively for most tasks. The transactionID parameter should be a value already agreed upon between the script and the destination application. Any number of key, value parameter pairs may be provided, including zero (none). The type of each parameter value determines the corresponding descriptor type in the outgoing Apple event. For all non-binary values, the descriptor type will be typeOf (value). For a binary value, the descriptor type will be getBinaryType (value). Thus, if you need to send a value with a different descriptor type than Frontier's default, you can coerce the value to a binary value, and then use setBinaryType to specify the desired type. Since most standard DDE events have an associated "ack" message, you will typically need to define a handler for the return event in the system.verbs.traps.DDE table, and process the response asynchronously.
|
| See Also |
appleEvent
|
| Prev | Next | Basic Verbs > DDEEvent |
