![]() ![]() Select a configuration on the dialog to load the Animazoo animations. The ZHAO II appears in the bottom right corner of your screen.ģ. Drag the 'ZHAO' object from your inventory onto your avatar. What you must do is drag the embedded objects to your inventory, and then from there drag into the second notecard.ZHAO-II instructions Animazoo customers: Don't for get to check your special animation by pressing 'page down' whilst wearing the ZHAO II!Ģ. ![]() Tip! While it appears that the contents of one notecard, text and embedded objects, can manually be copied from one notecard to a second notecard, in fact you won't be able to save that second notecard. Notecards can contain embedded assets, such as textures, landmarks, etc. To enable this, see: Editing someone else's scripts and notecards. In the course of shared projects, you may often need to let team members access notecards in objects owned by you, or need yourself to access notecards in objects owned by them. Key kQuery integer iLine = 0 string notecard_name = "Configuration" key notecard_key = NULL_KEY config_init () Sharing Notecard Access This script assumes that there is a notecard named "Configuration" in the object's inventory, and that one or more lines of text are stored in the notecard. (It will have a new key, and this will trigger reading it to get the changes.) If something else changes in the object's inventory, then the change is ignored and the configuration notecard is not re-read. The configuration notecard is read when the script is started, or when the configuration notecard itself changes. ![]() The following script illustrates this technique. This can be exploited in a script, to detect changes to a notecard and ignore other changes in an object's inventory. (The avatar's or object's inventory will not contain a reference to the old notecard any more - it is updated to reference the key of the new notecard.) The user probably thinks it is the same notecard object, but it is really an entirely new object. This means that when you are editing the notecard, you are actually creating a new notecard with an entirely different key than the original notecard. However internally within the Second Life asset server, notecard objects are immutable. If you create a notecard, then you can easily edit the notecard and save changes. (They don't appear to be immutable, but they really are.) Only the first 255 bytes of each line are returned.There is an illustration of the procedure here: Notecard_reading. As it comes into the script, it is captured in the dataserver event, during which event you parse the information and assign it to variables. To pull information from a notecard, you use the llGetNotecardLine function. Doing this negates both the need to distribute proprietary scripts with modify privileges, and the need for customers to edit scripts (which most find frightening.) Scripted products that are sold, however, often use instead a notecard as the place where customers can change parameters to meet their individual needs. opening sounds for drawers, etc.) are usually set and changed right in the script by editing the script. In public domain scripts released with modify privileges, operational parameters (e.g. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |