Talk:Getting started with LSL
Jump to navigation Jump to search
- Is there a reason the code isn't indented? I badly whitespaced code makes it hard to sit still; like walking into someones house and finding a picture hanging crooked on the wall. Maybe whitespace should be mentioned somewhere in the article too... Strife Onizuka 09:41, 1 February 2007 (PST)
- I didn't want to touch the indentation until we got syntax highlighting, (which is here now, wow took 10 months) I'll clean these up -- Blueman Steele 05:50, 17 December 2007 (PST)
- Moved the page, it's all the rage to have spaces in names. As to the capitalization of the name thats not my can of worms. Strife Onizuka 09:46, 1 February 2007 (PST)
- Code sample doesn't match what the article is saying. "The code above contains 2 comments, 1 state, 2 events and 2 functions. Lets look at them individually." Where's the two comments?
- Fixed it, I had the idea of commenting the code but decided instead to show it in its original form. -- Blueman Steele 05:46, 17 December 2007 (PST)
- RESET SCRIPTS IN SELECTION" etc. is greyed out How do I activate these options ?
- Could be a number of things including permissions or if you have the right object (or sub object selected) Blueman Steele 05:54, 17 December 2007 (PST)
- In the On/ Off example, shouldn't it be touch_end, rather than touch_start? - Kessalta Blackburn 16:55, 28 November 2009 (UTC)
- That depends on your preference. Consider the following scenario: You click the left mouse button, hold it clicked for 5 seconds, then release it. The moment you start to click it, touch_start is triggered, for the next five seconds, touch is triggered repeatedly over and over again, when you release the mouse button, touch_end is triggered.
Generelly, people expect inworld items to react on touch_start, since it's commonly used (maybe because it's part of the default script). But you can also script your device to react on touch_end, when it is what you prefer. -- (talk|contribs) 18:45, 28 November 2009 (UTC)