Second Life Wiki - User contributions [en]

Category:LSL Alpha

2010-10-30T08:00:13Z

Aria Twig: same.. terminology

{{LSL Header|ml=*}}
The term "Alpha" refers to how translucent an object (or, in this case, a prim) is. In Second Life, the alpha property is set by the scripting functions [[llSetAlpha]], [[llSetLinkAlpha]], [[llSetPrimitiveParams]], and [[llSetLinkPrimitiveParams]]. These functions use a [[float]] value. When set to '''0.0''', the object/prim is fully invisible. When set to '''1.0''', the object is opaque.
Sometimes, [[Resident]]s refer to a transparent [[texture]] as ''alpha texture''. This is a texture with an alpha map, not to be confused with this prim property. See [[llSetTexture]] and [[TEXTURE_TRANSPARENT]] instead.

==Build Mode==
In Build Mode, the alpha is represented by a percentage, ranging from '''0%''' to '''90%'''.
('''Note''': The '''90%''' cap is for viewers that have been officially released by Linden Labs)
==Examples==
Below are examples on how one may set the alpha of an object.
{|cellspacing="0" cellpadding="6" border="1" style="border: 1px solid #aaaaaa; margin: 1em 1em 1em 0pt; background-color: #F8F8FF; border-collapse: collapse"
!style="background-color: #D2D3FF" | Function
!style="background-color: #D2D3FF" | LSL Example
!style="background-color: #D2D3FF" | Description
|-
| [[llSetAlpha]]
| <lsl>llSetAlpha(1.0, ALL_SIDES);</lsl>
| This will set the object's sides' alpha to opaque, or '''0%'''.
|-
| [[llSetLinkAlpha]]
| <lsl>llSetLinkAlpha(LINK_SET, 0.0, ALL_SIDES);</lsl>
| This will set link-set's alpha to transparent, or '''100%'''. ('''Note''': The Viewers released by Linden Labs are unable to set the alpha of an object to fully transparent without a script; the limit is caped at '''90%''')
|-
| [[llSetPrimitiveParams]]
| <lsl>llSetPrimitiveParams([PRIM_COLOR, ALL_SIDES, llGetColor(ALL_SIDES), 0.5]);</lsl>
| This will set the object's alpha to translucent, or '''50%'''.
|-
| [[llSetLinkPrimitiveParams]]
| <lsl>llSetLinkPrimitiveParams(LINK_SET, [PRIM_COLOR, ALL_SIDES, llGetColor(ALL_SIDES), 0.5]);</lsl>
| This will set the link-set's alpha to translucent, or '''50%'''.
|-
|}

{{LSLC|}}{{LSLC|Face|*Alpha}}

Category:LSL Alpha

2010-10-30T07:55:45Z

Aria Twig: same, opaque fix

{{LSL Header|ml=*}}
The term "Alpha" refers to how opaque or transparent an object (or, in this case, a prim) is. In Second Life, the alpha property is set by the scripting functions [[llSetAlpha]], [[llSetLinkAlpha]], [[llSetPrimitiveParams]], and [[llSetLinkPrimitiveParams]]. These functions use a [[float]] value. When set to '''0.0''', the object/prim is fully invisible. When set to '''1.0''', the object is opaque.
Sometimes, [[Resident]]s refer to a transparent [[texture]] as ''alpha texture''. This is not to be confused with this prim property. See [[llSetTexture]] and [[TEXTURE_TRANSPARENT]] instead.

==Build Mode==
In Build Mode, the alpha is represented by a percentage, ranging from '''0%''' to '''90%'''.
('''Note''': The '''90%''' cap is for viewers that have been officially released by Linden Labs)
==Examples==
Below are examples on how one may set the alpha of an object.
{|cellspacing="0" cellpadding="6" border="1" style="border: 1px solid #aaaaaa; margin: 1em 1em 1em 0pt; background-color: #F8F8FF; border-collapse: collapse"
!style="background-color: #D2D3FF" | Function
!style="background-color: #D2D3FF" | LSL Example
!style="background-color: #D2D3FF" | Description
|-
| [[llSetAlpha]]
| <lsl>llSetAlpha(1.0, ALL_SIDES);</lsl>
| This will set the object's sides' alpha to opaque, or '''0%'''.
|-
| [[llSetLinkAlpha]]
| <lsl>llSetLinkAlpha(LINK_SET, 0.0, ALL_SIDES);</lsl>
| This will set link-set's alpha to fully transparent, or '''100%'''. ('''Note''': The Viewers released by Linden Labs are unable to set the alpha of an object to fully transparent without a script; the limit is caped at '''90%''')
|-
| [[llSetPrimitiveParams]]
| <lsl>llSetPrimitiveParams([PRIM_COLOR, ALL_SIDES, llGetColor(ALL_SIDES), 0.5]);</lsl>
| This will set the object's alpha to translucent, or '''50%'''.
|-
| [[llSetLinkPrimitiveParams]]
| <lsl>llSetLinkPrimitiveParams(LINK_SET, [PRIM_COLOR, ALL_SIDES, llGetColor(ALL_SIDES), 0.5]);</lsl>
| This will set the link-set's alpha to translucent, or '''50%'''.
|-
|}

{{LSLC|}}{{LSLC|Face|*Alpha}}

Category:LSL Alpha

2010-10-30T07:45:00Z

Aria Twig: /* Examples */ misuse of 'opaque' and percentages

{{LSL Header|ml=*}}
The term "Alpha" refers to how opaque or transparent an object (or, in this case, a prim) is. In Second Life, the alpha property is set by the scripting functions [[llSetAlpha]], [[llSetLinkAlpha]], [[llSetPrimitiveParams]], and [[llSetLinkPrimitiveParams]]. These functions use a [[float]] value. When set to '''0.0''', the object/prim is fully invisible. When set to '''1.0''', the object is non-transparent.
Sometimes, [[Resident]]s refer to a transparent [[texture]] as ''alpha texture''. This is not to be confused with this prim property. See [[llSetTexture]] and [[TEXTURE_TRANSPARENT]] instead.

==Build Mode==
In Build Mode, the alpha is represented by a percentage, ranging from '''0%''' to '''90%'''.
('''Note''': The '''90%''' cap is for viewers that have been officially released by Linden Labs)
==Examples==
Below are examples on how one may set the alpha of an object.
{|cellspacing="0" cellpadding="6" border="1" style="border: 1px solid #aaaaaa; margin: 1em 1em 1em 0pt; background-color: #F8F8FF; border-collapse: collapse"
!style="background-color: #D2D3FF" | Function
!style="background-color: #D2D3FF" | LSL Example
!style="background-color: #D2D3FF" | Description
|-
| [[llSetAlpha]]
| <lsl>llSetAlpha(1.0, ALL_SIDES);</lsl>
| This will set the object's sides' alpha to opaque, or '''0%'''.
|-
| [[llSetLinkAlpha]]
| <lsl>llSetLinkAlpha(LINK_SET, 0.0, ALL_SIDES);</lsl>
| This will set link-set's alpha to fully transparent, or '''100%'''. ('''Note''': The Viewers released by Linden Labs are unable to set the alpha of an object to fully transparent without a script; the limit is caped at '''90%''')
|-
| [[llSetPrimitiveParams]]
| <lsl>llSetPrimitiveParams([PRIM_COLOR, ALL_SIDES, llGetColor(ALL_SIDES), 0.5]);</lsl>
| This will set the object's alpha to translucent, or '''50%'''.
|-
| [[llSetLinkPrimitiveParams]]
| <lsl>llSetLinkPrimitiveParams(LINK_SET, [PRIM_COLOR, ALL_SIDES, llGetColor(ALL_SIDES), 0.5]);</lsl>
| This will set the link-set's alpha to translucent, or '''50%'''.
|-
|}

{{LSLC|}}{{LSLC|Face|*Alpha}}

LlList2CSV

2010-10-29T19:45:53Z

Aria Twig: fixed a wikipedia link to disambiguation

{{LSL_Function
|func_id=195|func_sleep=0.0|func_energy=10.0
|func=llList2CSV|return_type=string|p1_type=list|p1_name=src
|func_footnote=More precisely the values are separated with a comma and a space (", "). 
This function's functionality is equivalent to <code style="white-space: nowrap;">[[llDumpList2String]]('''src''', ", ");</code> 
The result of this function is more or less the {{Wikipedia|Comma-separated_values|CSV}} format, but it does not conform in all its details. 
To reverse the process use [[llCSV2List]]. But see the Caveat.
|func_desc
|return_text=of comma separated values taken in order from '''src'''.
|spec
|caveats=*[[llCSV2List]] will not reverse the process if there are commas in any of the original strings. One way around this is to first use [[llEscapeURL]] on any user-supplied strings before adding them to the list. [[llUnescapeURL]] will reverse [[llEscapeURL]].
|constants
|examples=<lsl>default
{
state_entry()
{
list my_list = [1, 2.0, "a string", llGetPos(), llGetRot(), llGetOwner()];
llOwnerSay(llList2CSV(my_list));
}
}</lsl>
|helpers
|also_functions={{LSL DefineRow||[[llCSV2List]]}}
{{LSL DefineRow||[[llDumpList2String]]}}
{{LSL DefineRow||[[llParseString2List]]}}
{{LSL DefineRow||[[llParseStringKeepNulls]]}}
|also_events
|also_tests
|also_articles={{LSL DefineRow||[[Typecast]]}}
|notes
|permission
|negative_index
|sort=List2CSV
|cat1=List
|cat2=String
|cat3=Data Conversion
|cat4=CSV
}}

LlCSV2List

2010-10-29T19:45:02Z

Aria Twig: fixed a wikipedia link to disambiguation

{{LSL_Function
|func_id=196|func_sleep=0.0|func_energy=10.0
|func=llCSV2List|return_type=list|p1_type=string|p1_name=src
|func_footnote=
To convert a list into a comma-separated string use [[llList2CSV]]. 
Do not confuse this function with the {{Wikipedia|Comma-separated_values|CSV}} format, it is ''not'' the CSV format.
|func_desc=This function takes a string of values separated by commas, and turns it into a list.
|return_text=made by parsing '''src''', a string of comma separated values.
|spec=
=== Vectors & Rotations ===
Anything between "<" and ">" is considered a single value regardless of the existence of a comma between.

This ensures that [[vector]]s and [[rotation]]s get treated as a single value, with no additional cleanup needed afterward.

Note, though, that for every "<" there needs to be a corresponding ">" or it will consume the rest of the string. For example,
{{{!}}
{{LSL DefineRow|| <code>llCSV2List("<>,>,a")</code>|returns <code>["<>", ">", "a"]</code>|(Second ">" is isolated)}}
{{LSL DefineRow|| <code>llCSV2List("<<>,>,a")</code>|returns <code>["<<>,>", "a"]</code>|(Regularly paired)}}
{{LSL DefineRow|| <code>llCSV2List("<<<>,>,a")</code>|returns <code>["<<<>,>,a"]</code>|(Third "<" lost its opposite one)}}
{{!}}}

=== Types ===

The function makes no assumptions about what the list entry types should be, all elements in the resulting list will be strings. It is important to know that the llList2* functions implicit typecasts do not work the same as explicit typecast. The following table gives code examples for each type that will yield the best results.

{{{!}} {{Prettytable|style=margin-top:0;}}
{{!}}- {{Hl2}}
! Target
! Code
! Description
{{!}}-
{{!}}[[integer]]
{{!}}<code>(integer)[[llList2String]](mlist, mint)</code>
{{!}}[[llList2Integer]] does not support the hex format
{{!}}-
{{!}}[[float]]
{{!}}<code>(float)[[llList2String]](mlist, mint)</code>
{{!}}[[llList2Float]] does not support the scientific or hexadecimal notations
{{!}}-
{{!}}[[string]]
{{!}}<code>[[llList2String]](mlist, mint)</code>
{{!}}Always Safe
{{!}}-
{{!}}[[key]]
{{!}}<code>[[llList2Key]](mlist, mint)</code>
{{!}}Always Safe
{{!}}-
{{!}}[[vector]]
{{!}}<code>(vector)[[llList2String]](mlist, mint)</code>
{{!}}[[llList2Vector]] will return a zero vector
{{!}}-
{{!}}[[rotation]]
{{!}}<code>(rotation)[[llList2String]](mlist, mint)</code>
{{!}}[[llList2Rot]] will return a zero rotation
{{!}}}

=== Whitespace ===

llCSV2List consumes the first leading space from all values :

<lsl>list tmp = llCSV2List("first , second , third");
//returns ["first ","second ","third"]
//not ["first "," second "," third"]</lsl>
|caveats=
* If a "<" does not have a matching ">", the remainder of the string will be a single value, even if the "<" is in the middle of the value, see [[#Vectors_.26_Rotations|Vectors & Rotations]] for further details.
* All items in the returned list are strings.
* If an empty string is parsed, the result will a list containing an empty string: [""] (not an empty list).
|constants
|examples=
<lsl>default
{
state_entry()
{
string csv = "first,second,third";
list my_list = llCSV2List(csv);
llOwnerSay("CSV: " + csv);
integer i;
integer num_list=llGetListLength(my_list);
for (i=0; i<num_list; ++i)
{
llOwnerSay("my_list[" + (string)i + "]: " + llList2String(my_list,i));
}
}
}</lsl>
|helpers
|also_functions={{LSL DefineRow||[[llList2CSV]]|}}
{{LSL DefineRow||[[llDumpList2String]]|}}
{{LSL DefineRow||[[llParseString2List]]|}}
{{LSL DefineRow||[[llParseStringKeepNulls]]|}}
|also_events
|also_tests
|also_articles={{LSL DefineRow||[[Typecast]]|}}
|notes=To use separators other than commas (especially if you can't predict when a user might have sneaked a comma into data they supply the script), use [[llParseString2List]] instead, which allows you to specify separators other than commas. [[llParseString2List]] unfortunately does not support the special parsing required for handling rotations and vectors, nor does it consume leading and trailing whitespace.
|permission
|negative_index
|sort=CSV2List
|cat1=List
|cat2=String
|cat3=Data Conversion
|cat4=CSV
}}

Category:LSL Key

2010-10-27T18:26:09Z

Aria Twig: linkified llGetKey

{{LSL Header|ml=*}}{{LSLC|}}{{LSLC|Types}}

A key is a unique identifier in Second Life for anything mostly, be it a prim, avatar, texture, etc.

You may see key referred to as [[UUID]], UID, "Asset UUID", or "asset-ID."

The key itself is formed of hexidecimal characters (a-f and 0-9) and each section of the key is broken up by dashes.

An example key:
<pre>"a822ff2b-ff02-461d-b45d-dcd10a2de0c2"</pre>

'''Getting a Key'''

There are several ways to acquire the key of something: 
1) Having someone supply it to you; 
2) Using a native LSL function such as [[llGetKey]], etc. 
3) In your inventory, right-clicking over something and choosing "Copy Asset UUID." Note this will only work on items that you have full permissions to.

'''Converting Keys'''

When a key is supplied to you as a text string, you convert it to the key data type like this:

(key)"a822ff2b-ff02-461d-b45d-dcd10a2de0c2";

'''Testing for a valid key'''

To test for a valid key, just do this:

<pre>if(uuid){
//do something
}
</pre>

if(uuid) will only return true if it is supplied a key that is both (A) valid, and (B) NOT a NULL_KEY.

Tip! In techy talk, this method is called "passing it as the parameter for a {{LSLGC|Conditional|conditional}}"

Here is an example of how to build a function around this:

<lsl>
integer isKey(key in) {
if(in) return 2;
return (in == NULL_KEY);
}
</lsl>

'''Caveats'''

<code>if (uuid)</code> is a special case. Keys cannot be converted to integers, so logical operators such as <code>!</code>, <code>||</code> and <code>&&</code> cannot be used with keys.

If you wish to do <code>if (!uuid) // Some action</code> then you can use a simple workaround like so: <code>if (uuid) {} else // Some action</code>. This is particularly useful if we wish to discard invalid string content (i.e - ensure that a key is actually a key) like so:<lsl>if (uuid) {} else if (uuid != NULL_KEY) uuid = NULL_KEY;</lsl>

== Extended Key Operations ==
These functions have been created and contributed by LSL users to perform operations not covered by built-in LSL functions.

{|{{Prettytable}}
|+
|-{{Hl2}}
!function
!purpose
|-
|| [[GenerateKey]] || Generates an MD5-based (version 3) type UUID. Useful for identifying link-messages and for other purposes.
|-
|| [[GenUUID]] || Generates a UUID based on PHP com_create_guid.
|}

Linden Lab Official talk:Age Verification FAQ

2010-10-26T19:13:59Z

Aria Twig: Created page with '==Loophole== "Absolutely no personal information that is supplied for the automated age verification process is stored or otherwise retained by Linden Lab or its verification pa...'

==Loophole==

"Absolutely no personal information that is supplied for the automated age verification process is stored or otherwise retained by Linden Lab or its verification partner Aristotle-Integrity. We keep only an indicator that tells us whether there was a positive match for the information you have provided.

Thus, this information will be used only for the purpose of verifying that a Resident is an adult, and will not be transferred or retained unless that is required by law, i.e., pursuant to a law enforcement investigation and proper legal process."

The way this is phrased, Linden can save personally identifying information from your verification, and use it to identify the same person verifying two avatars that are otherwise unconnected. It doesn't say that no personally identifying information is saved, just information you put directly into the form. And it doesn't say that the indicator/code can't tell them other things, just that it's all they save and one thing that it tells them. It could save a hash from the form or something else personally identifying in that code. It uses words like 'no personal information' and 'only keep an indicator that tells us' which is either a directly misleading loophole, or an accident. Either way it should be fixed. [[User:Aria Twig|Aria Twig]] 19:13, 26 October 2010 (UTC)