Difference between revisions of "LlSetNotecard"
Jump to navigation
Jump to search
(New page: integer llSetNotecard(string name, array data); Saves the content of the {{LSLG|Array}} data back as lines to the notecard name. Returns 0 if saving fails or 1 if ok.) |
|||
| Line 3: | Line 3: | ||
Saves the content of the {{LSLG|Array}} data back as lines | Saves the content of the {{LSLG|Array}} data back as lines | ||
to the notecard name. Returns 0 if saving fails or 1 if ok. | to the notecard name. Returns 0 if saving fails or 1 if ok. | ||
---- | |||
{{LL}} has refused on many occasions over the years to implement any function that results in writing or changing the contents of notecards. The reason given for this is that under the current implementation, when notecards are changed, a new asset is created, which is perfectly logical as they don't know how many copies of a notecard exist (updating one copy should not update all copies). The alternatives are to use script memory or offsite storage via {{LSLGC|Email}}, {{LSLGC|XML-RPC}} or {{LSLGC|HTTP}}. -- [[User:Strife Onizuka|Strife Onizuka]] 16:18, 27 July 2007 (PDT) | |||
Latest revision as of 16:18, 27 July 2007
integer llSetNotecard(string name, array data);
Saves the content of the Array data back as lines to the notecard name. Returns 0 if saving fails or 1 if ok.
Linden Lab has refused on many occasions over the years to implement any function that results in writing or changing the contents of notecards. The reason given for this is that under the current implementation, when notecards are changed, a new asset is created, which is perfectly logical as they don't know how many copies of a notecard exist (updating one copy should not update all copies). The alternatives are to use script memory or offsite storage via Email, XML-RPC or HTTP. -- Strife Onizuka 16:18, 27 July 2007 (PDT)