Difference between revisions of "Talk:LlDialog"
(zzzzz) |
|||
Line 4: | Line 4: | ||
: Can you use a function like this to find long strings? Then the user will not have to guess what button is bad Somebody check my work please, I am sleepy as always. | : Can you use a function like this to find long strings? Then the user will not have to guess what button is bad Somebody check my work please, I am sleepy as always. | ||
<lsl> | <lsl>integer GetStringBytes(string s) { | ||
integer GetStringBytes(string s) { | list chopped = llParseString2List(llEscapeURL("*" + s), ["%"], []); | ||
return llStringLength((string)chopped) - llGetListLength(chopped) - 1; | |||
}</lsl> | }</lsl> | ||
:--[[User:Cerise Sorbet|Cerise Sorbet]] 10:03, 27 November 2009 (UTC) | :--[[User:Cerise Sorbet|Cerise Sorbet]] 10:03, 27 November 2009 (UTC) | ||
:: I was too sleepy. Maybe this time. --[[User:Cerise Sorbet|Cerise Sorbet]] 11:06, 27 November 2009 (UTC) | |||
---- | ---- |
Revision as of 03:06, 27 November 2009
Telling an end user that the max length of a button label is 24 bytes ... well, not overly helpful. But there is the problem of what what characters translate to how many bytes. Still, is there any way we can give examples of characters?
Chaz Longstaff 05:18, 27 November 2009 (UTC)
- Can you use a function like this to find long strings? Then the user will not have to guess what button is bad Somebody check my work please, I am sleepy as always.
<lsl>integer GetStringBytes(string s) {
list chopped = llParseString2List(llEscapeURL("*" + s), ["%"], []); return llStringLength((string)chopped) - llGetListLength(chopped) - 1;
}</lsl>
- --Cerise Sorbet 10:03, 27 November 2009 (UTC)
- I was too sleepy. Maybe this time. --Cerise Sorbet 11:06, 27 November 2009 (UTC)
Strife, Chaz here. Most ordinary users in SL, and most user documentation in SL, refer to dialog boxes in SL as menus. While that may be as technically inaccurate as referring to a tomato as a vegetable, people don't look for tomatoes in between the apples and bananas at their green grocer (grin), and they are going to come here looking for info on menus, not dialogue boxes. I think we need to at least acknowledge the word menu, even if we do correct them about its usage right away. (I also dislike how people use the word less when they should be using fewer, but that is also just the way it is, sadly :} )Chaz Longstaff 18:17, 15 July 2008 (PDT)
- Very good point. I'll also keep a lookout for improper uses of "less". -- Strife Onizuka 18:32, 15 July 2008 (PDT)
The Wiki mentions that clicking on a button causes the value to be chatted on the specified channel, but doesn't clarify whether it's simply said(llSay) or shouted(llShout). It does mention that errors will be shouted on the Debug Channel, but I think it's important to clarify this within the Wiki. --Deimos Damone
- I have reworded the applicable caveat to clarify the functionality. -- Strife (talk|contribs) 11:49, 15 October 2008 (PDT)
It may be worth including some explicit explanation of the difference between bytes and unicode characters, especially since the inworld error messages somewhat ambiguously talk about characters, when in fact referring to bytes. -- Tali Rosca 10:45, 15 October 2008 (PDT)
- Many functions use byte limits and not character limits. I think it would be better to make the word "byte" a link to a (new?) subsection of the string article where that can be better addressed. It would be inappropriate to duplicate this information on multiple articles, it would end up clogging the articles. That said, I'll try to find the best method for presenting this information; as you point out the current caveat is inadequate and more information is needed. -- Strife (talk|contribs) 11:49, 15 October 2008 (PDT)
- I agree that the actual explanation shouldn't be here, but a link should be fairly prominent, since this is the most likely place people will run into the difference. Tali Rosca 12:03, 15 October 2008 (PDT)