Difference between revisions of "LlDeleteKeyValue/ja"

From Second Life Wiki
Jump to navigation Jump to search
(copy from english(Todo: need translate to japanese))
 
m
Line 1: Line 1:
[[Category:Experience Tools]]
[[Category:Experience Tools/ja]]
{{LSL_Function
{{LSL_Function
|inject-2=
|inject-2=
Line 6: Line 6:
|func=llDeleteKeyValue
|func=llDeleteKeyValue
|func_desc=Start an asynchronous transaction to delete a key-value pair associated with the script's {{LSLGC|Experience}} with the given key ({{LSLPT|k}}).
|func_desc=Start an asynchronous transaction to delete a key-value pair associated with the script's {{LSLGC|Experience}} with the given key ({{LSLPT|k}}).
|func_footnote=If the key does not exist the [[dataserver]] will return a failure along with the error [[XP_ERROR_STORAGE_EXCEPTION]].
|func_footnote=If the key does not exist the [[dataserver/ja]] will return a failure along with the error [[XP_ERROR_STORAGE_EXCEPTION]].
|return_type=key|return_subtype=handle
|return_type=key|return_subtype=handle
|return_text=that can be used to identify the corresponding [[dataserver]] event to determine if this command succeeded or failed and the results.
|return_text=that can be used to identify the corresponding [[dataserver/ja]] event to determine if this command succeeded or failed and the results.
|p1_type=string|p1_name=k|p1_desc=The key for the key-value pair
|p1_type=string|p1_name=k|p1_desc=The key for the key-value pair
|also_functions=
|also_functions=
*[[llGetExperienceErrorMessage]]
*[[llGetExperienceErrorMessage/ja]]
*[[llCreateKeyValue]]
*[[llCreateKeyValue/ja]]
*[[llReadKeyValue]]
*[[llReadKeyValue/ja]]
*[[llUpdateKeyValue]]
*[[llUpdateKeyValue/ja]]
*[[llDeleteKeyValue]]
*[[llDeleteKeyValue/ja]]
*[[llDataSizeKeyValue]]
*[[llDataSizeKeyValue/ja]]
*[[llKeyCountKeyValue]]
*[[llKeyCountKeyValue/ja]]
*[[llKeysKeyValue]]
*[[llKeysKeyValue/ja]]
|examples=<source lang="lsl2">key trans;
|examples=<source lang="lsl2">key trans;
default
default
Line 46: Line 46:
     }
     }
}</source>
}</source>
|cat1=Experience
|cat1=Experience/ja
|cat2=Experience/Data
|cat2=Experience/Data/ja
|cat3=Dataserver
|cat3=Dataserver/ja
}}
}}

Revision as of 02:54, 8 October 2023

Summary

Function: key llDeleteKeyValue( string k );

Start an asynchronous transaction to delete a key-value pair associated with the script's Experience with the given key (k).
Returns a handle (a key) that can be used to identify the corresponding dataserver/ja event to determine if this command succeeded or failed and the results.

• string k The key for the key-value pairThe key for the key-value pair

If the key does not exist the dataserver/ja will return a failure along with the error XP_ERROR_STORAGE_EXCEPTION.

For this function to work, the script must be compiled into an Experience.

Specification

Dataserver

The dataserver callback parameters are:

String Components
• integer success A boolean specifying if the transaction succeeded (1) or not (0).
• integer error An XP_ERROR_* flag that describes why the operation failed.
• string value The value for the key-value pair. Maximum 2047 characters, or 4095 if using Mono. Note! This value may contain commas.

Caveats

  • If you recompile a script that was previously associated with an Experience but do so with a client that lacks the ability to compile scripts into an experience the script will lose the associated Experience.

Examples

key trans;
default
{
    state_entry()
    {
        trans = llDeleteKeyValue("FOO");
    }

    dataserver(key t, string value)
    {
        if (t == trans)
        {
            // our llDeleteKeyValue transaction is done
            list result = llCSV2List(value);
            if (llList2Integer(result, 0) == 1)
            {
                // the key-value pair was successfully deleted
                llSay(0, "New key-value pair was deleted");
            }
            else
            {
                // the key-value pair was not deleted
                llSay(0, "Key-value failed to delete: " + llList2String(result, 1) );
            }
        } 
    }
}

Notes

Compiling

For a script to be associated with an Experience...

  • It must be compiled with a client that is Experience aware,
  • The "Use Experience" checkbox must be checked,
  • And one of the users Experience keys selected.
KBcaution.png 重要 Not all TPVs have this functionality.

Deep Notes

Signature

function key llDeleteKeyValue( string k );