call | ||||||||||
Type | command | |||||||||
Dictionary | LCS | |||||||||
Library | LiveCode Script | |||||||||
Syntax |
| |||||||||
Summary | ||||||||||
Introduced | 1.0 | |||||||||
OS | mac, windows, linux, ios, android | |||||||||
Platforms | desktop, server | |||||||||
Parameters |
| |||||||||
Example |
| |||||||||
Related | Property: defaultStack, script Command: do, insert script, send, start using Function: params, value Glossary: command, double quote, execute, handler, message, message path, object, object reference, parameter, pass, statement, trap, variable Control Structure: pass | |||||||||
Description | Use the call command to use a handler that's not in the normal message path. The call command sends a handler message to the object. If the script of the object doesn't trap the handler message, the message is passed to the next object in the object's message path. When executing a handler invoked by the call command the defaultStack remains the same as it was when the call command was issued. Therefore any object references in the called handler are evaluated in the context of the call command that invoked the handler. For example, button 3 may commonly refer to button 3 of the current card of the stack from which the target handler was called. This differs from the send command which temporarily changes the context so that object references are evaluated in the context of the object containing the target handler.
| |||||||||
Tags | messages |