send | |||||||||||||
Type | command | ||||||||||||
Dictionary | LCS | ||||||||||||
Library | LiveCode Script | ||||||||||||
Syntax |
| ||||||||||||
Summary | |||||||||||||
Introduced | 1.0 | ||||||||||||
OS | mac, windows, linux, ios, android | ||||||||||||
Platforms | desktop, server, mobile | ||||||||||||
Parameters |
| ||||||||||||
Example |
| ||||||||||||
Values |
| ||||||||||||
Related | Property: callbacks, backgroundBehavior Message: mouseUp Keyword: word Control Structure: function Function: result, pendingMessages Command: debugDo, dispatch, call, cancel Glossary: object, literal string, return, evaluate, execute, command, LiveCode, double quote, trigger, message path, message, parameter, statement, handler | ||||||||||||
Description | Use the send command to override the normal message path, or to delay a command until a specified time. The message can be either the name of a handler or a LiveCode statement. If the message is a literal string containing more than one word (for example, if it includes parameters, or if it is a multi-word command), it must be enclosed in doublequotes. If the
and a button on the stack named "Button" with script
clicking the button would result in an answer dialog first saying "Button" as the
When the send command is used the stack containing the target handler temporarily becomes the defaultStack. All object references in the message are evaluated in the current context i. e. the defaultStack. Therefore references within the message that refer to "this card" or "this stack" will be referring to the card or stack where the target handler is located. It is a parse error to specify a time when using the
| ||||||||||||
Tags | messages |