Difference between revisions of "User talk:Domitan Redenblack"
| Line 13: | Line 13: | ||
== llGetSubString IS, IS, IS unpredictable == | == llGetSubString IS, IS, IS unpredictable == | ||
Sorry Strife, but (.., -3, -5) returns the entire string for me... sometimes. Hard to predict. I was using this on a "(string)objectKey" and I tried 10 different ways. If "start > end" I get unpredictable results. | Sorry Strife, but (.., -3, -5) returns the entire string for me... sometimes returns a weird part. Hard to predict. I was using this on a "(string)objectKey" and I tried 10 different ways. If "start > end" I get unpredictable results. | ||
Latest revision as of 01:17, 5 September 2011
llGetSubString is predictable
I take it you had some trouble with the Ranges & Indexes section, it is a bit complicated and the functionality it describes is strange. However it is predictable.
Quick crash course: <lsl>llGetSubString("abcdefg", 2, 4) == "cde" llGetSubString("abcdefg", 4, 2) == "abcefg" llGetSubString("abcdefg", -5, -3) == "cde" llGetSubString("abcdefg", -3, -5) == "abcefg"</lsl>
Suffice it to say, it is not a bug. However, changing the behavior at this point would break 7 years of existing content. -- Strife (talk|contribs) 00:32, 5 September 2011 (PDT)
llGetSubString IS, IS, IS unpredictable
Sorry Strife, but (.., -3, -5) returns the entire string for me... sometimes returns a weird part. Hard to predict. I was using this on a "(string)objectKey" and I tried 10 different ways. If "start > end" I get unpredictable results.