llGetNotecardLineSync
string llGetNotecardLineSync(string name,// Name of the notecard in the prim's inventory, or a UUID.integer line// Zero-based line number to request.
);- Returns
string- Energy
- 10
Synchronously reads the line index line of the notecard name from the region's cache, immediately returning its text without raising a dataserver event. Returns 'NAK' if not cached or 'EOF' if out of bounds.
Gets the line of the notecard name from the region’s notecard cache immediately without raising a dataserver event.
Returns EOF if line is past the end of the notecard.
string result = llGetNotecardLineSync("", 0);Specification
Section titled “Specification”This function returns a string containing the requested line from a notecard in prim inventory, without the need for an asynchronous dataserver event, if the notecard is cached/known in its entirety by the simulator. This speeds up acessing notecard lines tremendously, and allows for near instantaneous random access.
If the notecard does not exist it returns the constant NAK and will shout a message to the debug channel. If the notecard has not been previously cached on the simulator it will return the NAK constant.
Notecards are cached into a fixed-size buffer, with the oldest (least-recently read) notecard getting removed first. It is not safe to assume a notecard has been previously cached. Data for a previously cached notecard may be dropped from the cache at any time, especially on a busy server.
Caveats
Section titled “Caveats”- If notecard contains embedded inventory items (such as textures and landmarks),
EOFwill be returned, regardless of the line requested. - If the requested line is longer than 1024 bytes (not characters),
llGetNotecardLineSyncwill only return the first 1024 bytes of the line. - To check that the returned line has not been truncated, use the example snippet on
llStringToBase64to check the number of bytes returned byllGetNotecardLineSync. If the string is exactly 1024 bytes, it may have been truncated. - Do not use
llStringLengthfor this, because strings in LSL support multi-byte characters (UTF-8 for LSL-2, UTF-16 for Mono). - A
dataserverevent does not get raised. Therefore, other scripts in the linkset are unaware of the processed notecard lines. - Since this function does not idle the script while waiting for a
dataserverevent, garbage collection will not run while loading an entire notecard by callingllGetNotecardLineSyncin a loop. For large notecards, you can quickly run out of free memory, even if you overwrite each line as you read it. - This does not occur with
llGetNotecardLine, which runs garbage collection while waiting for thedataserverevent. - This can be mitigated using
timers (any length will do), but notllSleep, which also blocks garbage collection.
Examples
Section titled “Examples”Example 1
18 collapsed lines
string NOTECARD_NAME = "notecard";key READ_KEY = NULL_KEY;
default{
touch_start(integer total_number) { READ_KEY = llGetNumberOfNotecardLines(NOTECARD_NAME); }
dataserver(key request, string data) { if (request == READ_KEY) { integer count = (integer)data; integer index;
for (index = 0; index < (count+1); ++index) { string line = llGetNotecardLineSync(NOTECARD_NAME, index); if (line == NAK) {14 collapsed lines
llOwnerSay("---NAK---"); } else if (line == EOF) { llOwnerSay("---EOF---"); } else { llOwnerSay(line); } } } }}Following example to call a normal dataserver notecard read using llGetNotecardLine if llGetNotecardlineSync fails with a NAK. Keep in mind to clear any lists you are reading data into when using the following example to keep from corrupting the integrity of the list data.
// llGetNotecardLineSync example with fall back to the old dataserver read// if llGetNotecardLineSync fails with a NAK.
string NOTECARD_NAME = "notecard";15 collapsed lines
key READ_KEY = NULL_KEY;
key noteCard_qry;integer noteCard_line;
default{
state_entry() { // read the notecards number of lines to the // simulators cache memory READ_KEY = llGetNumberOfNotecardLines(NOTECARD_NAME); }
dataserver(key request, string data) { // read notecards using the new llGetNotecardLineSync function // from simulator cache. if (request == READ_KEY) { integer count = (integer)data; integer index;
for (index = 0; index < (count+1); ++index) { string line = llGetNotecardLineSync(NOTECARD_NAME, index); if (line == NAK) { // Got a notecard NAK meaning llGetNotecardLineSync had and error. // falling back to the old dataserver event to read notecards. llOwnerSay("---NAK---");34 collapsed lines
noteCard_qry = llGetNotecardLine(NOTECARD_NAME, noteCard_line); return; // return is needed to break the for/next loop once the NAK is encountered. } else if (line == EOF) { // End of notecard. llOwnerSay("---EOF---"); } else { // do work here. llOwnerSay(line); } } }
// old system takes over if a NAK is encountered. if(request == noteCard_qry) { if(data == EOF) { // End of notecard encountered. llOwnerSay("EOF encountered"); } else { // process normal notecard line, then read the next line // of the notecard. llOwnerSay(data); noteCard_qry = llGetNotecardLine(NOTECARD_NAME, ++noteCard_line); } } }}Here is a more compact implementation that returns to using llGetNotecardLineSync whenever possible:
17 collapsed lines
string file_name;integer file_line_number;key file_request;
default { state_entry() { file_name = llGetInventoryName(INVENTORY_NOTECARD, 0); // get the name of the first notecard in the object's inventory }
touch_start(integer n) { // start reading text when the object is touched (you'll probably want to move these lines to another place depending on your needs): file_line_number = 0; file_request = llGetNotecardLine(file_name, file_line_number); }
dataserver(key id, string message) { if (id == file_request) { while (message != EOF && message != NAK) { llOwnerSay(message); // do useful things with the text here message = llGetNotecardLineSync(file_name, ++file_line_number); } if (message == NAK)6 collapsed lines
file_request = llGetNotecardLine(file_name, file_line_number); if (message == EOF) llOwnerSay("End of file."); } }}See also
Section titled “See also”Functions
Section titled “Functions”Original wiki source
Some wiki templates and tables need their original context. View this article on the Second Life Wiki. Technical wording and examples are retained from the source; historical guidance may differ from current behavior.