Release Notes/Second Life Release Candidate/1.21
< Release Notes | Second Life Release Candidate
Jump to navigation
Jump to search
Revision as of 14:33, 18 August 2008 by Ramzi Linden (talk | contribs) (New page: Category:Release Notes == Release Notes for Second Life 1.21(0) August 21st, 2008 == '''New features:''' * The option in the Tools menu > Recompile Scripts to support compiling of sc...)
Release Notes for Second Life 1.21(0) August 21st, 2008
New features:
- The option in the Tools menu > Recompile Scripts to support compiling of scripts in Mono vs. LSL
- NOTE: This requires a region running server version 1.24 & higher to work
- Moderation for Group Text and Group Voice
- NOTE: This requires a region running server version 1.24 & higher to work
- This viewer introduces the feature of "moderated" voice & text conversations. (All previous versions of Second Life have included an "open" form of voice and text conversations.)
- Moderation is only available in Group text and Group voice chat, for any formal Group in Second Life.
- Moderation does not apply to any type of conversation (either text or voice) in Local Chat proximity or one-to-one conversations
- Moderation does not apply to any type of ad hoc Group conversation, either text or voice.
- When a particular conversation is moderated, Residents will see new UI elements in the Communicate window that reflects the "moderated" conversation they are in.
- There is a new ability 'Moderate Group Chat' available to the Roles in Groups
- Moderator is an ability that is automatically part of the Group Owner and Group Officer roles, but can this be changed or added to other roles
- The Moderator ability can be seen and managed in the existing Group Information window
- A moderator does not have the ability to create other moderators during a conversation
- The moderator ability is a permanent ability (until changed by a Group owner, officer, etc.).
- Only the moderators will see the new Moderation controls during applicable Group IM/Calls.
- A new UV-picking feature that allows a prim to report where on its surface/texture it has been clicked.
- NOTE: This requires a region running server version 1.24 & higher to work
- This project adds the following new LSL commands:
- llDetectedTouchUV() - returns the UV coordinates of the point touched.
- llDetectedST() - returns the surface coordinates of the point touched.
- llDetectedTouchFace() - returns the face of the point touched.
- llDetectedTouchPos() - returns the world coordinates of the point touched.
- llDetectedTouchNormal() - returns the surface normal of the point touched.
- llDetectedTouchBinormal() - returns the surface bi-normal of the point touched.
- These commands are valid in the events touch_start(), touch(), and touch_end(). in the case of touch(), where events are triggered as long as the mouse is held down - each event has the current surface point data (allowing grabbing, sliders, levers, and all sorts pseudo GUI builds.)
- IMPORTANT: NOTES ON COMPATIBILITY
- Only avatars who click on an object from a supported viewer (version 1.21.0 or higher) will be able to pass the coordinates of their mouseclick to the LSL call.
- If an avatar clicks on the object with an older viewer, the coordinates passed will be reported as -1,-1
- Scripters take note! You can build your scripts to detect the value -1,-1 as an "Undefined" touch. The creator of such objects must decide how to handle, message to, or warn avatars who are not running a supported viewer for their content.