Difference between revisions of "Link message"
Jump to navigation
Jump to search
All Issues ~ Search JIRA for related Bugs
m (typo) |
Lady Sumoku (talk | contribs) m (Replaced old <LSL> block with <source lang="lsl2">) |
||
| Line 12: | Line 12: | ||
*If '''str''' and '''id''' are bigger than available memory the script will crash with a Stack-Heap Collision. | *If '''str''' and '''id''' are bigger than available memory the script will crash with a Stack-Heap Collision. | ||
|examples= | |examples= | ||
< | <source lang="lsl2"> | ||
//This is just an example script, you shouldn't handle touches within single script this way. | //This is just an example script, you shouldn't handle touches within single script this way. | ||
| Line 27: | Line 27: | ||
} | } | ||
} | } | ||
</ | </source> | ||
|helpers= | |helpers= | ||
< | <source lang="lsl2"> | ||
// This is just an example script, you shouldn't handle link message within single script this way. | // This is just an example script, you shouldn't handle link message within single script this way. | ||
| Line 49: | Line 49: | ||
} | } | ||
} | } | ||
</ | </source> | ||
|also_header | |also_header | ||
|also_events | |also_events | ||
Revision as of 01:24, 22 January 2015
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Description
Event: link_message( integer sender_num, integer num, string str, key id ){ ; }| 29 | Event ID |
Triggered when the script receives a link message that was sent by a call to llMessageLinked. llMessageLinked is used to send messages from one script to another.
| • integer | sender_num | – | The link number of the prim that contained the script that called llMessageLinked. | |
| • integer | num | – | Second parameter of the llMessageLinked call. | |
| • string | str | – | Third parameter of the llMessageLinked call. | |
| • key | id | – | Fourth parameter of the llMessageLinked call. |
id is often used as a second string field (in LSL the key type is implemented as a string with just custom operators). Typecasting between string and key types has no effect on the data contained. The sizes of str and id are only limited by available script memory.
Caveats
- 64 link_message events can queue, past that, they are silently dropped! Don't do too much in the event if they might be coming in fast.
- sender_num does not reflect how a message was sent, there is no way to know if it was sent with a LINK_* flag or the specific link number.
- If str and id are bigger than available memory the script will crash with a Stack-Heap Collision.
Examples
//This is just an example script, you shouldn't handle touches within single script this way.
default
{
touch_start(integer num_detected)
{
llMessageLinked(LINK_THIS, 0, llDetectedName(0), llDetectedKey(0));
}
link_message(integer source, integer num, string str, key id)
{
llWhisper(0, str + " (" + (string)id + ") touched me!");
}
}
Useful Snippets
// This is just an example script, you shouldn't handle link message within single script this way.
default
{
// To propagate an unlimited number of arguments of any type.
// Presumed, the separator string isn't used in any source string!
state_entry()
{
list my_list = [1, 2.0, "a string", <1, 2, 3>, <1, 2, 3, 4>, llGetOwner()];
string list_parameter = llDumpList2String(my_list, "|"); // Produce a | delimited string from the list
llMessageLinked(LINK_THIS, 0, list_parameter, NULL_KEY);
}
link_message(integer sender_num, integer num, string list_argument, key id)
{
list re_list = llParseString2List(list_argument, ["|"], [""]); // Convert the string back to a list
}
}
Notes
 |
Important: A script can hear its own link messages. |
See Also
Functions
| • | llMessageLinked |
Deep Notes
Signature |
|---|
event void link_message( integer sender_num, integer num, string str, key id ); |