Second Life Wiki - User contributions [en]

User:MartinRJ Fayray/de

2025-07-24T10:34:42Z

MartinRJ Fayray: Year

[[Image:MartinRJ_Small_New.png|right|thumb|50x55px]]
'''MartinRJ''' ('''nick: [http://world.secondlife.com/resident/97980bee-d865-4100-80e7-9763e53e8a6a MartinRJ Fayray] in [[Second Life]]'''), ist ein österreichischer [[Furry]], der seit vielen Jahren in Deutschland lebt. Er betreibt mehrere populäre deutschsprachige [[Furry]]-Gruppen in [[Second Life]]: [https://world.secondlife.com/group/f3c6593e-55f7-b6d5-9c81-47d3515b743b German Furs] (die größte deutschsprachige Furrygruppe in SL), [https://world.secondlife.com/group/1d4268a3-297a-e68d-ac0c-c8b5389135ae DACH Furries] und [https://world.secondlife.com/group/11a186d7-8f12-9031-6d21-66fb6c6a0146 Austrian Furry].

MartinRJ ist Programmierer, Sicherheitsforscher („Hacker“) und langjähriger Mitwirkender am [[Second Life Viewer]]. Zudem organisiert er virtuelle Events und Konzerte in [[Second Life]].

Er besitzt und verwaltet die deutsche Furry-Hauptsim [http://maps.secondlife.com/secondlife/Wander%20Beachside/183/132/22 "DACH Furries"] (Regionname „Wander Beachside“), mit großzügigem Strandbereich, Partyzone, Skyboxen, BDSM-Haus und einer großen Sandbox. Direkt angrenzend befindet sich seine Rental-Sim [http://maps.secondlife.com/secondlife/DACH%20Furries/182/144/32 "DACH Furries Oase"] (Regionsname „DACH Furries“), auf der Parzellen zum Selbstkostenpreis angeboten werden.

Besucher sind herzlich eingeladen, den einzigartigen und intelligenten Wolf-Bot „Lupo“ auf "DACH Furries" zu testen. Traut euch ruhig, ihm auch einmal etwas schmuddeligere Fragen zu stellen – er liebt es!

Übrigens steht gelegentlich ein Klon von MartinRJ persönlich am Strand der DACH Furries, wenn er selbst gerade anderswo in SL-Clubs unterwegs ist. Rawr! 🐾

[[Image:MartinRJ_3.PNG|center|thumb|220px|[http://world.secondlife.com/resident/97980bee-d865-4100-80e7-9763e53e8a6a MartinRJ Fayray] auf seiner Heimat-Sim [http://maps.secondlife.com/secondlife/Wander%20Beachside/183/132/22 DACH Furries], 2025]]

Webseite (deutschsprachige SL-Furry-Community-Linksammlung): [https://german-furs.de German-Furs.de]

{{Jira Reporter}}
[[Category:People]]
[[Category:Second Life characters]]
[[Category:Austria]]
[[Category:Germany]]

User:MartinRJ Fayray/de

2025-07-24T10:34:13Z

MartinRJ Fayray: Updated images

[[Image:MartinRJ_Small_New.png|right|thumb|50x55px]]
'''MartinRJ''' ('''nick: [http://world.secondlife.com/resident/97980bee-d865-4100-80e7-9763e53e8a6a MartinRJ Fayray] in [[Second Life]]'''), ist ein österreichischer [[Furry]], der seit vielen Jahren in Deutschland lebt. Er betreibt mehrere populäre deutschsprachige [[Furry]]-Gruppen in [[Second Life]]: [https://world.secondlife.com/group/f3c6593e-55f7-b6d5-9c81-47d3515b743b German Furs] (die größte deutschsprachige Furrygruppe in SL), [https://world.secondlife.com/group/1d4268a3-297a-e68d-ac0c-c8b5389135ae DACH Furries] und [https://world.secondlife.com/group/11a186d7-8f12-9031-6d21-66fb6c6a0146 Austrian Furry].

MartinRJ ist Programmierer, Sicherheitsforscher („Hacker“) und langjähriger Mitwirkender am [[Second Life Viewer]]. Zudem organisiert er virtuelle Events und Konzerte in [[Second Life]].

Er besitzt und verwaltet die deutsche Furry-Hauptsim [http://maps.secondlife.com/secondlife/Wander%20Beachside/183/132/22 "DACH Furries"] (Regionname „Wander Beachside“), mit großzügigem Strandbereich, Partyzone, Skyboxen, BDSM-Haus und einer großen Sandbox. Direkt angrenzend befindet sich seine Rental-Sim [http://maps.secondlife.com/secondlife/DACH%20Furries/182/144/32 "DACH Furries Oase"] (Regionsname „DACH Furries“), auf der Parzellen zum Selbstkostenpreis angeboten werden.

Besucher sind herzlich eingeladen, den einzigartigen und intelligenten Wolf-Bot „Lupo“ auf "DACH Furries" zu testen. Traut euch ruhig, ihm auch einmal etwas schmuddeligere Fragen zu stellen – er liebt es!

Übrigens steht gelegentlich ein Klon von MartinRJ persönlich am Strand der DACH Furries, wenn er selbst gerade anderswo in SL-Clubs unterwegs ist. Rawr! 🐾

[[Image:MartinRJ_3.PNG|center|thumb|220px|[http://world.secondlife.com/resident/97980bee-d865-4100-80e7-9763e53e8a6a MartinRJ Fayray] auf seiner Heimat-Sim [http://maps.secondlife.com/secondlife/Wander%20Beachside/183/132/22 DACH Furries], 2024]]

Webseite (deutschsprachige SL-Furry-Community-Linksammlung): [https://german-furs.de German-Furs.de]

{{Jira Reporter}}
[[Category:People]]
[[Category:Second Life characters]]
[[Category:Austria]]
[[Category:Germany]]

User:MartinRJ Fayray

2025-07-24T10:31:07Z

MartinRJ Fayray: Updated images

[[Image:MartinRJ_Small_New.png|right|thumb|50x55px]]
'''MartinRJ''' ('''nick: [http://world.secondlife.com/resident/97980bee-d865-4100-80e7-9763e53e8a6a MartinRJ Fayray] in [[Second Life]]'''), is an Austrian [[Furry]] living in Germany for many years. He manages several popular German-language [[Furry]] groups in [[Second Life]]: [https://world.secondlife.com/group/f3c6593e-55f7-b6d5-9c81-47d3515b743b German Furs] (the largest German-speaking furry group in SL), [https://world.secondlife.com/group/1d4268a3-297a-e68d-ac0c-c8b5389135ae DACH Furries], and [https://world.secondlife.com/group/11a186d7-8f12-9031-6d21-66fb6c6a0146 Austrian Furry].

MartinRJ is a programmer, security researcher ("hacker"), and longtime contributor to the [[Second Life Viewer]]. He also organizes virtual events and concerts in [[Second Life]].

He owns and manages the German furry main region [http://maps.secondlife.com/secondlife/Wander%20Beachside/183/132/22 "DACH Furries"] (region name "Wander Beachside"), featuring a large beach area, party zone, skyboxes, BDSM house, and a spacious sandbox. Adjacent to this is his rental region [http://maps.secondlife.com/secondlife/DACH%20Furries/182/144/32 "DACH Furries Oase"] (region name "DACH Furries"), where plots are available at cost price.

Visitors are warmly invited to test the unique and intelligent wolf-bot "Lupo" at "DACH Furries". Feel free to ask him some naughty questions – he enjoys it!

Occasionally, a clone of MartinRJ himself can be found standing at the DACH Furries beach while he's busy exploring other SL clubs. Rawr! 🐾

[[Image:MartinRJ 3.PNG|center|thumb|220px|[http://world.secondlife.com/resident/97980bee-d865-4100-80e7-9763e53e8a6a MartinRJ Fayray] at his home region [http://maps.secondlife.com/secondlife/Wander%20Beachside/183/132/22 DACH Furries], 2025]]

Website (German-language SL furry community link collection): [https://german-furs.de German-Furs.de]

{{Jira Reporter}}
[[Category:People]]
[[Category:Second Life characters]]
[[Category:Austria]]
[[Category:Germany]]

File:MartinRJ Small New.png

2025-07-24T10:29:38Z

MartinRJ Fayray: Profile of MartinRJ

== Summary ==
Profile of MartinRJ

File:MartinRJ 3.PNG

2025-07-24T10:28:37Z

MartinRJ Fayray: MartinRJ in his home in Secod Life.

== Summary ==
MartinRJ in his home in Secod Life.

User:MartinRJ Fayray

2025-07-24T10:07:26Z

MartinRJ Fayray: Update after over a decade

[[Image:MartinRJ_Small_New.GIF|right|thumb|50x60px]]
'''MartinRJ''' ('''nick: [http://world.secondlife.com/resident/97980bee-d865-4100-80e7-9763e53e8a6a MartinRJ Fayray] in [[Second Life]]'''), is an Austrian [[Furry]] living in Germany for many years. He manages several popular German-language [[Furry]] groups in [[Second Life]]: [https://world.secondlife.com/group/f3c6593e-55f7-b6d5-9c81-47d3515b743b German Furs] (the largest German-speaking furry group in SL), [https://world.secondlife.com/group/1d4268a3-297a-e68d-ac0c-c8b5389135ae DACH Furries], and [https://world.secondlife.com/group/11a186d7-8f12-9031-6d21-66fb6c6a0146 Austrian Furry].

MartinRJ is a programmer, security researcher ("hacker"), and longtime contributor to the [[Second Life Viewer]]. He also organizes virtual events and concerts in [[Second Life]].

He owns and manages the German furry main region [http://maps.secondlife.com/secondlife/Wander%20Beachside/183/132/22 "DACH Furries"] (region name "Wander Beachside"), featuring a large beach area, party zone, skyboxes, BDSM house, and a spacious sandbox. Adjacent to this is his rental region [http://maps.secondlife.com/secondlife/DACH%20Furries/182/144/32 "DACH Furries Oase"] (region name "DACH Furries"), where plots are available at cost price.

Visitors are warmly invited to test the unique and intelligent wolf-bot "Lupo" at "DACH Furries". Feel free to ask him some naughty questions – he enjoys it!

Occasionally, a clone of MartinRJ himself can be found standing at the DACH Furries beach while he's busy exploring other SL clubs. Rawr! 🐾

[[Image:MartinRJ_2.PNG|center|thumb|220px|[http://world.secondlife.com/resident/97980bee-d865-4100-80e7-9763e53e8a6a MartinRJ Fayray] at his home region [http://maps.secondlife.com/secondlife/Wander%20Beachside/183/132/22 DACH Furries], 2024]]

Website (German-language SL furry community link collection): [https://german-furs.de German-Furs.de]

{{Jira Reporter}}
[[Category:People]]
[[Category:Second Life characters]]
[[Category:Austria]]
[[Category:Germany]]

User:MartinRJ Fayray/de

2025-07-24T10:04:59Z

MartinRJ Fayray: Created page / translation.

[[Image:MartinRJ_Small_New.GIF|right|thumb|50x60px]]
'''MartinRJ''' ('''nick: [http://world.secondlife.com/resident/97980bee-d865-4100-80e7-9763e53e8a6a MartinRJ Fayray] in [[Second Life]]'''), ist ein österreichischer [[Furry]], der seit vielen Jahren in Deutschland lebt. Er betreibt mehrere populäre deutschsprachige [[Furry]]-Gruppen in [[Second Life]]: [https://world.secondlife.com/group/f3c6593e-55f7-b6d5-9c81-47d3515b743b German Furs] (die größte deutschsprachige Furrygruppe in SL), [https://world.secondlife.com/group/1d4268a3-297a-e68d-ac0c-c8b5389135ae DACH Furries] und [https://world.secondlife.com/group/11a186d7-8f12-9031-6d21-66fb6c6a0146 Austrian Furry].

MartinRJ ist Programmierer, Sicherheitsforscher („Hacker“) und langjähriger Mitwirkender am [[Second Life Viewer]]. Zudem organisiert er virtuelle Events und Konzerte in [[Second Life]].

Er besitzt und verwaltet die deutsche Furry-Hauptsim [http://maps.secondlife.com/secondlife/Wander%20Beachside/183/132/22 "DACH Furries"] (Regionname „Wander Beachside“), mit großzügigem Strandbereich, Partyzone, Skyboxen, BDSM-Haus und einer großen Sandbox. Direkt angrenzend befindet sich seine Rental-Sim [http://maps.secondlife.com/secondlife/DACH%20Furries/182/144/32 "DACH Furries Oase"] (Regionsname „DACH Furries“), auf der Parzellen zum Selbstkostenpreis angeboten werden.

Besucher sind herzlich eingeladen, den einzigartigen und intelligenten Wolf-Bot „Lupo“ auf "DACH Furries" zu testen. Traut euch ruhig, ihm auch einmal etwas schmuddeligere Fragen zu stellen – er liebt es!

Übrigens steht gelegentlich ein Klon von MartinRJ persönlich am Strand der DACH Furries, wenn er selbst gerade anderswo in SL-Clubs unterwegs ist. Rawr! 🐾

[[Image:MartinRJ_2.PNG|center|thumb|220px|[http://world.secondlife.com/resident/97980bee-d865-4100-80e7-9763e53e8a6a MartinRJ Fayray] auf seiner Heimat-Sim [http://maps.secondlife.com/secondlife/Wander%20Beachside/183/132/22 DACH Furries], 2024]]

Webseite (deutschsprachige SL-Furry-Community-Linksammlung): [https://german-furs.de German-Furs.de]

{{Jira Reporter}}
[[Category:People]]
[[Category:Second Life characters]]
[[Category:Austria]]
[[Category:Germany]]

Flycam

2015-11-03T17:58:36Z

MartinRJ Fayray: /* Nathan Zetkin - Space Mouse wireless - 3DxWare v10.0.19 - Windows 7 64 bit */ Update for version v10.2.9 of the SpaceMouse Wireless

{{Help
|BugFixes=
|Avatar=
|Object=
|LandSim=
|Community=
|Viewer=*
|Communication=
|Multimedia=
|Navigation=*
|Misc=
|Description=
|Wiki=
|Glossary=
}}
== How do I enable Joystick Flycam? ==
In [[1.20|Second Life 1.20]] and newer where it became a formally supported feature, View menu > Joystick Flycam (Alt-Shift-F). To customize settings, go to Edit menu > Preferences > Input & Camera tab and click Joystick Setup.

In order versions (like 1.9.1), [[Advanced menu]] > Joystick Flycam.

Press Esc to leave Flycam mode.

== How do I use Flycam with the 3DConnexion SpaceNavigator? ==
'''[[SpaceNavigator|See the SpaceNavigator page.]]'''

== Instructions ==
[[Image:Joystick-Configuration.png|384px|thumb|SpaceNavigator Defaults]] The following instructions were graciously provided by Runitai Linden and edited by Torley Linden. As of '''[[1.20|Second Life 1.20]], the Joystick Flycam, and specifically, [[SpaceNavigator]] compatibility, is officially supported'''.

: ''"I tested on a logitech cordless rumblepad 2 (PS2 controller clone) and got some great shots, but with only 4 axes, I couldn't move straight up or down. The device that started this whole mess was a 3D connexion 6-axis controller, so the camera works well with it, but I'm not fond of the device because it acts more like a 3D cursor than a joystick, hence the '3D Cursor' check box. Enjoy!" -Runitai Linden''

Joystick Flycam offers 6 degrees of freedom that you can bind to various actions:

* '''Y-Axis''' - Move camera up/down
* '''X-Axis''' - Move camera left/right
* '''Z-Axis''' - Move camera forward/backward
* '''Yaw''' - Turn left/right
* '''Pitch''' - Look up/down
* '''Roll''' - Bank left/right
* '''Zoom In/Out'''

The little output graph shows you the values Second Life is getting from your joystick on each axis. Take the number of the axis you want and set the action you want it to go to to that axis number. '''Set an action axis to "-1" to turn the action off.'''

'''Dead Zone''' - These values tell Second Life to ignore values below a certain threshold to avoid drift.

'''Scale''' - These values adjust sensitivity. If you find it difficult to move with precision, use lower scale values.

'''3D Cursor''' - Gives values as cursor positions instead of push amounts. Should be enabled for SpaceNavigator and similar devices.

'''Direct Zoom''' - Enable this to directly map values from your joystick to your FOV (Field Of Vision) instead of being treated as a delta. Off by default.

'''Auto Level''' - Keeps the camera up, vector sane — good if you feel dizzy and want the horizon to be level.

'''Feathering''' - Setting the slider all the way to the right will make the camera very rigid, giving complete control to the joystick. Setting the slider all the way to the left will make the camera very fluid like the camera weighs a lot; good for fly-by shots, not good for framing.

== Resident experiences ==
Have an intriguing Flycam story to tell? ''Share it here!''

=== Nalates Urriah - Win-7 64-bit SpaceNavigator Install ===
:: The information below got me started. But, it is possible to get the version 10 (v10) driver for the SpaceNavigator working and program the SpaceNavigator buttons. The quick and dirty install is to use version 3-18 legacy driver (Download: [http://www.3dconnexion.com/service/legacy-driver.html 3Dconnexion's Legacy Drivers]). To use the newer version 32 or 64 bit (current 64-bit: 3DxWare64_v10-1-4_r1818 as of 8/2014) you have to make a change in Windows Device Manager and manually create a profile for Second Life. It is a long explanation. The details are here: [http://blog.nalates.net/2014/08/28/3dconnextion-spacenavigator-v10-for-second-life Installing 3DConnextion SpaceNavigator v10 for Second Life]. [[User:Nalates Urriah|Nalates Urriah]] 07:42, 28 August 2014 (PDT)

:: Please click by the JIRA and Watch item: [https://jira.secondlife.com/browse/BUG-6049 BUG-6049] - Add Ability to select device in Joystick Config. If you have a good user case and have needed this feature please explain it in the comments and itemize the device or devices that ran you into the problem.

=== Nathan Zetkin - Space Mouse wireless - 3DxWare v10.0.19 - Windows 7 64 bit ===
(with much thanks to Zion Tristan)

''' Use Zion's instructions below to begin:'''

In Windows, go to ''Control Panel > Administrative Tools > Computer Management''. Select the ''Device Manager'' from the left pane, and then choose the ''Human Interface Devices'' and check to see if you have a device called ''3Dconnexion KMJ Emulator''. You may or may not be able to disable this device (''Properties > Driver > Disable''), but disable it if you can. Additionally, find a ''HID-compliant device'', ''HID-compliant game controller'', or ''HID-compliant consumer control device'', and check the ''Hardware ID'' (''Properties > Details > Hardware IDs''), looking for '''HID\3DXKMJ_HIDMINI&Col03''' as the topmost value. When you find the device, disable it from the ''Driver'' tab.

'''Editing the config file:'''

In the folder ''C:\Program Files\3Dconnexion\3DxWare\3DxWinCore64\Cfg'', you will find a file called ''joystick.xml''. Copy it and rename the new file to ''SecondLifeViewer.xml''. I use a free xml editor to edit xml files but just about any text editor should work. I made the following changes so that the top part looks like this:

<nowiki><AppCfg Default="true" xmlns="" CfgFormatVersion="1.0" ThisFileVersion="1.0">
<AppInfo>
<Name>Second Life</Name>
<VersionRange>
<Min>1.0</Min>
<Max>1.0</Max>
</VersionRange>
<ExecutableName>SecondLifeViewer.exe</ExecutableName>
<ApplicationIcon>SecondLifeViewer.ico</ApplicationIcon>
</nowiki>

Save the file and run Second Life.

'''Changing Second Life preferences:'''

Go to ''Preferences->Move & View->Other Devices''. You should see at the top, that the '''Enable Joystick: SpaceMouse Wireless''' is checked. The other parameters are set as shown below:

{| class="" {{Prettytable}}
|- {{Hl2}}
!
! '''Avatar'''
! '''Build'''
! '''Flycam'''
|-
||X Scale
||0.50
||0.30
||8.00
|-
||Y Scale
||0.50
||0.30
||8.00
|-
||Z Scale
||0.50
||0.30
||8.00
|-
||Pitch Scale
||0.50
||0.30
||2.00
|-
||Yaw Scale
||4.00
||0.30
||2.00
|-
||Roll Scale
||
||0.30
||0.30
|}

I check the box '''Auto Level''' and leave '''Direct Zoom''' and '''3D Cursor''' unchecked. For '''Control Modes''', I leave '''Build''' unchecked and '''Avatar''' and '''Flycam''' checked.

I hope this helps. 3Dconnexion says the Second Life is no longer supported, but the Space Mouse is a joy to use in Second Life and is indispensable when building.

----

'''Update (2015-11-03) by MartinRJ Fayray'''

You need to make some slight modifications to the instructions above, with newer versions (3DxWare64 v10.2.9).

Open the config-file JoystickTemplate.xml with notepad,

(you have to open notepad AS ADMINISTRATOR, rightclick Notepad.exe->Run as administrator),

and replace the AppInfo part in the top with this:

<code><AppInfo></code>

:: <code><Name>STR_SECONDLIFE</Name></code>

:: <code><VersionRange></code>

:::: <code><Min>1.0.0.0</Min></code>

:::: <code><Max>1.0.0.0</Max></code>

:: <code></VersionRange></code>

:: <code><ExecutableName>SECONDLIFEVIEWER.exe</ExecutableName></code>

:: <code><InheritsFrom /></code>

:: <code><ApplicationIcon>SecondLifeViewer.ico</ApplicationIcon></code>

:: <code><Transport>KMJ</Transport></code>

:: <code><IgnoreMouseWheelInertia>true</IgnoreMouseWheelInertia></code>

<code></AppInfo></code>

and then save the file as SecondLifeViewer.xml in the same folder.

Afterwards you have to restart your PC, in order to apply the changes.

--[[User:MartinRJ Fayray|MartinRJ Fayray]] ([[User talk:MartinRJ Fayray|talk]]) 09:58, 3 November 2015 (PST)

=== Zion Tristan - SpacePilot Pro - 3DxWare v10 Beta 15 - Windows 8 ===
[[Image:SpacePilot%20Pro.png|right|thumb|SpacePilot Pro]]
The Beta 15 version of the 3DxWare v10 works quite well, however may require some tweaking in terms of removing the KMJ Emulator from the Devices list to make it work correctly.

In Windows, go to ''Control Panel > Administrative Tools > Computer Management''. Select the ''Device Manager'' from the left pane, and then choose the ''Human Interface Devices'' and check to see if you have a device called ''3Dconnexion KMJ Emulator''. You may or may not be able to disable this device (''Properties > Driver > Disable''), but disable it if you can. Additionally, find a ''HID-compliant device'', ''HID-compliant game controller'', or ''HID-compliant consumer control device'', and check the ''Hardware ID'' (''Properties > Details > Hardware IDs''), looking for '''HID\3DXKMJ_HIDMINI&Col03''' as the topmost value. When you find the device, disable it from the ''Driver'' tab.

I additionally note that the .xml file holding the settings for the profile you use with Second Life needs editing. If you create a profile for Second Life (highly recommended), navigate to the following directory: ''C:\Users\<your username>\AppData\Roaming\3Dconnexion\3DxWare\Cfg\secondlife.xml'' (Or your viewer of preference) and change the '''<Transport>DirectInput</Transport>''' to '''<Transport>S80</Transport>''', then save the file.

You may need to restart your computer for changes to take effect, but it should be pretty instantaneous. When you start up Second Life, you can go to the ''Properties > Move & View > Joystick Configuration'', and check the ''Enable Joystick: SpacePilot PRO 3Dmouse (or your joystick's name)''. I personally use the settings below:
{| class="" {{Prettytable}}
|- {{Hl2}}
!
! '''Avatar'''
! '''Build'''
! '''Flycam'''
|-
||X Scale
||1.00
||0.30
||20.00
|-
||Y Scale
||1.00
||0.30
||20.00
|-
||Z Scale
||1.00
||0.30
||20.00
|-
||Pitch Scale
||5.00
||0.30
||5.00
|-
||Yaw Scale
||5.00
||0.30
||5.00
|-
||Roll Scale
||
||0.30
||0.00
|}

I additionally have unchecked '''Direct Zoom''' and '''3D Cursor''', and these settings work fine for me.

I did notice that the "Fit" key on the actual device (thumb button, when used in the left hand) also makes the avatar jump, and I've found no way around this, so I use one of the other 39 buttons, and assign macro's to them to control me. I set the following buttons to do the following actions through the 3DxWare Properties:
{| class="" {{Prettytable}}
|- {{Hl2}}
! '''Button'''
! '''Action'''
|-
||R (lower right corner, right set of buttons)
||Flycam Toggle {{KeyCombo|alt=*|shift=*|F}}
|-
||F (lower left corner, right set of buttons)
||Escape (Reset camera position) {{KeyCombo|esc}}
|-
||ISO 1 (centre, right set of buttons)
||Fly toggle {{KeyCombo|F}}
|}

=== Kiptic Horsley - SpaceNavigator 3DxWare v10 ===
The new (currently beta) 3DxWare v10 puts everything on its head, so to make it work with
Second Life you need to change a few settings:

* In the 3Dconnextion Properties, create a new application profile for SL. Make sure you select ''Joystick'' as the profile template.
* In the Joystick configuration inside the SL viewer, change all XYZ etc. Scale values for "Avatar" to 1.00 (they have various values like 2.00, 0.10 and so on by default and this will not work well). You can always change this later if you like. You might want to increase the flycam XYZ scales a bit too, maybe 3.00 or so.
* Finally, '''uncheck 3D Cursor'''. This is very important, and completely contrary to everything anyone has said about SpaceNavigator inside SL before :)

Now it should work, enjoy!

Major gripe: left button can't be changed from that annoying 3Dx popup menu in the current 3DxWare beta, so you'll have to get along with only one button for now.

=== Illumine Demina - SpaceNavigator ===
Updated: 4/9/2008 per 1.20 "Dazzle" release

We have some nice new "joystick" support: these instructions describe use of the 3d_Connexion "Space Navigator."

Configuration options have been moved to the Edit -> Preferences menu item, "Input and Camera" tab. At the bottom of the page, select "Joystick Setup" and a new popup appears. Bottom right of this page, click "SpaceNavigator Defaults." For some, you might be all set... give it a try.

NOTE that in prior releases, the SpaceNavigator could only control the "Flycam", whereas now it can also control objects in Build/Edit mode ("Build" column) as well as Avatar motion ("Avatar" column). To enter Flycam mode select the View -> Joystick Flycam menu item, or keystroke Alt-Shift-F.

In Avatar mode, it seems the X/Y/Z scales have no effect - amy value other than 0 gives standard walk/run speeds. Pitch and Yaw scale cn be raised to 1.0 if you like to dance till you're dizzy... 0.3 seems about right to me. I leave all the zones at the defaults.

I'm not a dedicated builder... but it seems to me that aligning anything would be about impossible using this feature. I defer to others on this.

As a machinimatographer I like to make some changes to the defaults in the "FlyCam" column. First, decide if you want the SpaceNavigator to act as if you're moving 1) the object, or 2) the camera. The defaults move the camera, just as advertised. When you lift up the camera goes up - and the world goes down. I'm sure some get used to this with no issue, but I prefer the SpaceNavigator to operate as though I'm holding the world: lift up and the world raises, pull toward you and the world comes closer. Its entirely a matter of preference, but its weird how one can feel right and the other probably doesn't. For this behavior, all the numbers in the top half of the "Flycam" column get a minus "-" in front of them, inverting everything and giving you object mode. Most of my camera moves are around an avatar, so they are short and delicate. That means the scale numbers need to get smaller (in absolute value): X-Scale and Z-Scale become -0.6, Y-Scale becomes -0.2 (up and down is less quick) as do "Pitch Scale" and "Yaw Scale." I slightly increase deadzones to 0.03, except pitch goes to 0.1 to keep things a bit stabler. Feather slider goes all the way left (syrupy, not snappy), and give it a try.

Illumine )I(

=== Pre-1.20:
I made mine work (on Windows XP) by installing, configuring, and calibrating per the factory instructions, starting SL, and selecting the Client -> Joystick Flycam option. A popup appears... and my screen went wonky :) But after fiddling quite a bit I was able to operate using these settings:

First, this is a "3D cursor", so check that box. Then, check "auto-level", un-check "Direct Zoom", and set "Feathering" to the middle. Start here:

<pre>
x y z yaw pitch roll zoom
mapping 0 2 1 5 3 4 -1
scale .1 .05 .2 .05 .05 .01 0
deadzone .1 .1 .1 .1 .1 .1 1
</pre>

Try moving the navigator ... it may work ... else restart the application and re-enable Flycam.

Update as of Jan 2008:

When I first wrote this, the feathering slider was way weird... it needed to be pretty much left or it wouldn't work. As of windlight at this time, feathering works *much* better. Left is "mushy soft" and right is "snappy firm" ... season to taste :)

I updated the above settings to give a better ability to move forward and back (Z Axis) and better overall response. Love this!

If the motion seems weird, perhaps you'd prefer to use its inverse! In a typical 3D modeling approach, you move the controller just like you would model a model in your hand. In the inverse case, its more like you are holding and moving a camera. To really confuse yourself, set different axis in different senses :) You can reverse motion either in the controller software or in the SL Client -> Joystick Flycam option popup. To reverse an axis, simply enter a negative scale. Inverting makes a huge difference... try them both so you know which you like.

=== Tenebrous Pau - SpaceNavigator ===
Tenebrous Pau uses a [http://www.3dconnexion.com/forum/viewtopic.php?t=336 community-provided joystick driver] to connect the SpaceNavigator to SL. See [http://teneverse.blogspot.com/2007/07/blog-post.html this blog post] for Tenebrous' recommended settings with the RBC9 driver. 
'''Note:''' The RBC9 driver is not needed to make the SpaceNavigator work with SL; just use [http://www.3dconnexion.com/support/4a1.php the latest 3DConnexion driver].

The community-provided joystick driver is not compatible with 64-bit operating systems.

'''Note''': As of 11th April 2008, Tenebrous no longer uses the RBC9 driver, with the advent of Second Life client 1.20.0 84432. The SL viewer has built in support for the SpaceNavigator, without need for the RBC9 drivers, as per [[Flycam#Illumine_Demina.27s_Instructions|Illumine Demina's Instructions]] above.

=== Ganesha Xi - Space Navigator ===
[[Image:Space Nav settings.png|256px|right|thumb|My Flycam settings]]
After much frustration with this cool hardware I bought, I decided to further investigate settings. As I don't use it much to walk, only for fly cam, those are the only settings I changed.
Some advice if you are getting frustrated with your SpaceNav:
* Always get the latest driver. If your Space Nav is NOT glowing blue, it does not have the driver installed. See previous contributions.
* The default SpaceNav settings are "slow" (according to them), but are entirely too fast for the average user. Step them down some (such as in my picture)!
* Practice, practice, practice. The SpaceNav requires a gentle touch. The only way to fully master it is by practicing.
* Join the 3DConnexion Space Cadets group in SL. They are a friendly bunch!
* Yes, seeing a bunch of ]]]]]]]]]]]]][[[[[[[[[[[[[[[['s in your chat box when you "spin" left/right is common (and irritating). The only way I've found to fix it is to relog.

=== ZATZAi Asturias - Xbox 360 controller ===
[[Image:FlyCam360.jpg|256px|right|thumb|Suggested Flycam Settings for Xbox 360 Controller]]

It's also possible to use the FlyCam mode with the very popular Xbox 360 controller, provided you have one you can connect to your PC and the latest drivers (Works on XP & Vista) you're set for FlyCam. One thing to keep in mind with the 360 controller, is that it only supports five axis's, the joysticks each have two and the analog triggers together represent a fifth (Right trigger for negative left trigger for positive). The FlyCam only supports the first two buttons, so you can't use any other buttons on the 360 controller.

To the right you can see the settings I went with for my 360 controller after toying with it for a while, this allowed maximum mobility and smooth movement, also I used a larger than default dead zone on each input because the precision of the 360's joysticks called for it. Additionally 10% feathering, or so, was used as it greatly smoothed out camera movement while not suffering from the excessive sliding of the maximum setting.

'''Settings:'''

<pre>
x y z pitch yaw roll zoom
mapping 0 2 1 4 3 -1 -1

flycam scale 8.00 4.00 20.00 2.00 2.00 5.00 1.00
flycam deadzone 0.25 0.25 0.25 0.25 0.25 0.25 0.50
flycam feathering 10%

avatar scale 1.00 1.00 1.00 1.00 1.00
avatar deadzone 0.25 0.25 0.25 0.25 0.25 0.25
avatar feathering 5%

Direct Zoom Enabled
3D Cursor Disabled
Auto Level Enabled

Zoom Scale 1.00
Zoom Dead Zone 0.50

</pre>

With these settings you can push forwards and back on the left joystick to dolly the camera forwards and back, and left and right on the same joystick to dolly the camera left and right. To pitch the camera up or down push forward (To pitch down) or pull back (To pitch up) with the right joystick, or tilt the right joystick to the left or right to turn the camera to the left or right. To raise the camera pull in on the right trigger and to lower it pull in on the left trigger.

You'll find you have a slightly smaller field of vision which makes a nice effect for machinima with Direct Zoom enabled. You can disabled it or adjust the Zoom settings to alter it's appearance for close in or wide angle shots. I didn't put in any settings for Build as personally I don't use it (Note that while you can move things around very elegantly with flycam for build... only you will see the object move others will not until you stop moving the item). You will also be able to move your avatar with your joystick with these settings (That's why the Avatar column is checked). Not terribly useful for walking around but you'll find it fun for controlling vehicles, especially planes!

To activate or deactivate flycam mode press: {{KeyCombo|alt=*|shift=*|F}} (Or the '''A''' button on your controller)

=== Geneko Nemeth - Logitech Dual Action ===
This controller is similar in layout with the Xbox 360 Controller. It has 4 axis (shoulder buttons are not analog), 12 buttons and a D-pad, but Second Life does not support more than 2 buttons or Point-of-View hat, so the D-pad cannot be used under Windows (but can be used in Linux).

<pre>

Scales Whatever you like
Dead Zone At least 0.15

Direct Zoom Disabled
3D Cursor Disabled
Auto Level Disabled (Enable if you think turning around in flycam mode looks strange...)

</pre>

Left thumbstick to walk (Z) / turn around(yaw) 
Right thumbstick to fly (Y) / strafe (X).

== Related resources ==
* '''[[SpaceNavigator]]''' - Includes video demos.

[[Category: Tutorials]]

LlRequestPermissions

2015-02-24T21:03:54Z

MartinRJ Fayray: Added information about "Stop Animating Me".

{{LSL_Function
|inject-2={{Issues/SVC-1006}}{{Issues/SVC-8067}}{{LSL_Function/avatar|agent|sim=*}}
|func=llRequestPermissions|sort=RequestPermissions
|func_id=136|func_sleep=0.0|func_energy=10.0
|p1_type=key|p1_name=agent|p1_desc
|p2_type=integer|p2_name=permissions|p2_desc=Permission mask ([[Bit field|bitfield]] containing the permissions to request).
|func_desc=Ask {{LSLP|agent}} for {{LSLP|permissions}} to run certain classes of functions.
|func_footer=Script execution continues without waiting for a response. When a response is given, a [[run_time_permissions]] event is put in the event queue.
|return_text
|spec
|caveats=
<div>
* A dialog is presented to the agent to grant these permissions except when granted automatically as shown in the table above.
* If object is attached to agent, "automatic" permissions are granted without notification upon request.
* Permissions persist across state changes.
* Regardless of whether granting is automatic, you should always use the [[run_time_permissions]] event. Granting permissions takes time, and you shouldn't assume it's completed until the [[run_time_permissions]] handler gets invoked.
* The menu-option "Stop Animating Me" will release certain permissions (PERMISSION_TRIGGER_ANIMATION and PERMISSION_OVERRIDE_ANIMATIONS), if the script which holds these permissions is in the same region as the agent, and the script is not attached to the permission granter.
* Permissions do not accumulate.
** If a permission was requested with a previous call to this function and granted, then in subsequent call was not requested, that permission is released (lost).
** To request two or more permissions at the same time, use the bitwise OR <nowiki>(|) operator, e.g.:</nowiki> <lsl>llRequestPermissions(AvatarID, PERMISSION_TAKE_CONTROLS | PERMISSION_TRIGGER_ANIMATION)</lsl>
</div>
* Permissions are requested and granted separately for each script, even if they are located in the same object.
* It is currently not possible to request no permissions at all (see Issues below); as a workaround [[llResetScript]] can be used.
* Scripts may hold permissions for only one agent at a time. To hold permissions for multiple agents you must use more than one script.
* The result of granting permissions affects the return of [[llGetPermissions]] and [[llGetPermissionsKey]] immediately, despite the [[run_time_permissions]] event being queued, or dropped if the object's event queue is full.
* Permission request dialogs never time out.
** If a script makes two permission requests, which ever response is last is considered the granted permissions.
* The viewer limits permission requests from any agent to any other agent to 5 dialogs in 10 seconds
|notes=When an agent grants a script non-automatic permissions they will receive a notification (in chat) of - The '''name''' of the object that contains the script that has been granted perms, The name of the owner of the object, The location of the object in the order - Region name at '''position''' - and a statement of what permissions were granted. If the script that holds the permissions is in a child prim the '''name''' will be that of the child prim (not the object (root)) and '''position''' will be its [[llGetLocalPos|local]] position (relative to its root).
|examples=Request permission to animate an avatar
<source lang="lsl2">default
{
touch_start(integer detected)
{
llRequestPermissions(llDetectedKey(0), PERMISSION_TRIGGER_ANIMATION);
}
run_time_permissions(integer perm)
{
if (perm & PERMISSION_TRIGGER_ANIMATION)
{
llStartAnimation("sit");
llOwnerSay("animation will end in 5 seconds");
llSetTimerEvent(5.0);
}
}
timer()
{
llSetTimerEvent(0.0);
llStopAnimation("sit");
}
}</source>

To request two (or more) different permissions at the same time you can using the bitwise OR <nowiki>(|)</nowiki> or precompute the value.
<source lang="lsl2">llRequestPermissions(AvatarID, PERMISSION_TAKE_CONTROLS | PERMISSION_TRIGGER_ANIMATION);

integer perms = PERMISSION_TAKE_CONTROLS | PERMISSION_TRIGGER_ANIMATION;
llRequestPermissions(AvatarID, perms);</source>

|helpers
|also_events={{LSL DefineRow||[[run_time_permissions]]|Permission receiver event}}
|also_functions={{LSL DefineRow||[[llGetPermissions]]|Get the permissions granted}}
{{LSL DefineRow||[[llGetPermissionsKey]]|Get the avatar who granted permissions.}}
|also_articles={{LSL DefineRow||{{LSLGC|Permissions/Script|Script permissions}}|}}
|constants={{LSL Constants/Permissions}}
|cat1=Permissions/Script
|cat2=Dialog
|cat3
|cat4
|cat5
|cat6
}}

Category:LSL Functions/de

2014-09-10T22:04:59Z

MartinRJ Fayray: Punctuation

{{Multi-lang}}
{{LSL Header/de}}

Diese Kategorie beinhaltet die eingebauten LSL Funktionen.

== Wandlungsfähigkeit ==
Alle Typen in LSL sind unveränderlich (sie können nicht durch Nebeneffekte verändert werden). Variablen können nur durch Überschreiben verändert werden. Es gibt keine Möglichkeit indirekt einen Variablenwert zu verändern; die einzige Möglichkeit ist durch direkte Interaktion mit einem speichernden Operator (=, +=, -=, *=, /=, %=, ++, --).
*Standardfunktionen werden die Variablen, die sie als Parameter nutzen, '''niemals''' verändern.
*Von Usern erstellte Funktionen, welche die Werte von Parametern in der Funktion verändern, werden diese Veränderungen nicht in den Variablen speichern, die diese Parameter überliefert haben.
{{LSLC/de|Keywords}}{{LSLC/de|Flow Control}}{{LSLC/de}}

Category:LSL Functions/de

2014-09-10T22:03:49Z

MartinRJ Fayray: Fixed typos

{{Multi-lang}}
{{LSL Header/de}}

Diese Kategorie beinhaltet die eingebauten LSL Funktionen.

== Wandlungsfähigkeit ==
Alle Typen in LSL sind unveränderlich (sie können nicht durch Nebeneffekte verändert werden). Variablen können nur durch Überschreiben verändert werden. Es gibt keine Möglichkeit indirekt einen Variablenwert zu verändern; die einzige Möglichkeit ist durch direkte Interaktion mit einem speichernden Operator (=, +=, -=, *=, /=, %=, ++, --).
*Standardfunktionen werden die Variablen die sie als Parameter nutzen '''niemals''' verändern.
*Von Usern erstellte Funktionen, welche die Werte von Parametern in der Funktion verändern, werden diese Veränderungen nicht in den Variablen speichern, die diese Parameter überliefert haben.
{{LSLC/de|Keywords}}{{LSLC/de|Flow Control}}{{LSLC/de}}

Category:LSL Types/de

2014-09-10T21:42:47Z

MartinRJ Fayray: Added missing var:lang tag.

{{Multi-lang}}
{{LSL Header/de}}
===Einleitung===

Ein Datentyp (Englisch: type, auch: Datenart) ist die Klassifikation die eine bestimmte Art von Daten identifiziert, die bestimmt welche Werte für diesen Typ gültig sind.

Datentypen in [[LSL{{#var:lang}}|LSL]] können:

[[Integer{{#var:lang}}|Ganzzahlen]],

[[Float{{#var:lang}}|Fließkommazahlen]],

[[String{{#var:lang}}|Zeichenketten]],

[[Key{{#var:lang}}|Keys]] (Zeichenketten von bestimmter Länge),

[[Vector{{#var:lang}}|Vektoren]],

[[Rotation{{#var:lang}}|Rotationen]],

[[List{{#var:lang}}|Listen]]
sein.

Die Deklaration einer integer-Variable (Ganzzahl) definiert, dass diese Variable ausschließlich Ganzzahlen enthalten kann, bei dem hier verwendeten 32-bit Wertebereich entspricht das einer beliebigen Ganzzahl in dem Bereich zwischen {{LSL Hex|0x00000000}} und {{LSL Hex|0xFFFFFFFF}}.

===Beispiel===
<lsl>integer meineVariable = 123;</lsl>

{{LSLC/de|Types}}{{LSLC/de|Flow Control}}{{LSLC/de}}

Category:LSL Types/de

2014-09-10T21:06:00Z

MartinRJ Fayray: Created the page (translation from English)

{{Multi-lang}}
{{LSL Header/de}}
===Einleitung===

Ein Datentyp (Englisch: type, auch: Datenart) ist die Klassifikation die eine bestimmte Art von Daten identifiziert, die bestimmt welche Werte für diesen Typ gültig sind.

Datentypen in [[LSL]] können:

[[Integer{{#var:lang}}|Ganzzahlen]],

[[Float{{#var:lang}}|Fließkommazahlen]],

[[String{{#var:lang}}|Zeichenketten]],

[[Key{{#var:lang}}|Keys]] (Zeichenketten von bestimmter Länge),

[[Vector{{#var:lang}}|Vektoren]],

[[Rotation{{#var:lang}}|Rotationen]],

[[List{{#var:lang}}|Listen]]
sein.

Die Deklaration einer integer-Variable (Ganzzahl) definiert, dass diese Variable ausschließlich Ganzzahlen enthalten kann, bei dem hier verwendeten 32-bit Wertebereich entspricht das einer beliebigen Ganzzahl in dem Bereich zwischen {{LSL Hex|0x00000000}} und {{LSL Hex|0xFFFFFFFF}}.

===Beispiel===
<lsl>integer meineVariable = 123;</lsl>

{{LSLC/de|Types}}{{LSLC/de|Flow Control}}{{LSLC/de}}

LSL Operators/de

2014-09-08T06:45:50Z

MartinRJ Fayray: Fixed some missing translations, typos

{{Multi-lang}}
{{LSL Header/de}}
Operatoren sind Zeichen mit denen man Informationen aus Variablen auf vordefinierte Weise verarbeiten lassen kann. Eine (mathematische) Aktion kann auf eine oder zwei Operanden angewendet werden.
Ein einfaches Beispiel ist 1 + 2, wobei die Zahlen 1 und 2 die Operanden darstellen, und '''+''' ist der Operator.

{| bgcolor="#FFFFFF" border="1" cellspacing="2" cellpadding="6"
|- bgColor="#A7C1F2"
! Operator
! Beschreibung
! Anwendungsbeispiel
|-
| () || Klammern || a * (b + c)
|-
| [] || Eckige Klammern: Listen-Konstruktor || [a, 2, "das", 0.01]
|-
| (''typ'') || Typkonvertierung || nachricht = "Das Ergebnis lautet:" + (string) ergebnis;
|-
| ! ~ ++ -- || Logisches-NICHT, Bitweises-NICHT, Inkrement, Dekrement || zaehler++;
|-
| * / % || Multiplikation/Skalarprodukt, Division, Modulo/Kreuzprodukt || rest = (anzahl + 1)%5;
|-
| - || Subtraktion || eins = 3 - 2;
|-
| + || Addition oder String-Verknüpfung || zwei = 1+1;
text = "Hello" + "World";
|-
| + || Konkatenation oder Zusammenführung von Listen || meineListe = [1, 2, 3] + [4, 5];
neueListe = alteListe + zusatzListe;
|-
| << >> || Links Shift, Rechts Shift || acht = 4 << 1;
|-
| < <= > >= || Kleiner Als, Kleiner Als oder Gleich,
Größer Als, Größer Als oder Gleich
|| istFalsch = (6 <= 4);
|-
| == != || Vergleich auf Gleichheit, Vergleich auf Ungleichheit || istFalsch = ("dies" == "das");
|-
| & || Bitweises UND || null = 4 & 2;
vier = 4 & 4;
|-
| ^ || Bitweises XOR || null = 4 ^ 4;
sechs = 4 ^ 2;
|-
| <nowiki>|</nowiki> || Bitweises ODER || vier = 4 <nowiki>|</nowiki> 4;
sechs = 4 <nowiki>|</nowiki> 2;
|-
| <nowiki>||</nowiki> || Logisches ODER || istWahr = (FALSE <nowiki>||</nowiki> TRUE);
|-
| && ||Logisches UND || istFalsch = (FALSE && TRUE);
|-
| = += -= *= /= %= || Zuweisung || vier = 4;
|}

'''Anmerkung:''' Anders als in den meisten anderen Programmiersprachen die den C-Stil für '''&&''' und '''||''' Operatoren anwenden, werden '''beide''' Operanden '''immer''' ausgewertet. Zum Beispiel:

<lsl>if (TRUE || 1/0) llSay(PUBLIC_CHANNEL, "Aha!");</lsl>

führt zu einer Fehlermeldung, statt "Aha" auszugeben.

'''Anmerkung:''' Die ++ (Inkrement) und -- (Dekrement) - Operatoren wirken sich auf die Zahl entweder vor oder nach der Auswertung aus, je nachdem ob sie vor oder nach dieser Zahl stehen.

<lsl>integer count;
if(!(++count)) // Wird erhöht, und danach ausgewertet.
llSay(PUBLIC_CHANNEL, "Aha"); // Wird nicht ausgegeben.</lsl>

<lsl>integer count;
if(!(count++)) // Wird ausgewertet und danach erhöht.
llSay(PUBLIC_CHANNEL, "Aha"); // Wird ausgegeben.</lsl>

'''Anmerkung:''' Die Boole'schen Operatoren '''||''' und '''&&''' werden in der Auswertungs-Reihenfolge von LSL als gleichwertig angesehen.

'''Anmerkung:''' Die Auswertungsreihenfolge unterscheidet sich von der Auswertungsreihenfolge der meisten Programmiersprachen. Wenn der Wert von x im nachfolgenden Beispiel initial 1 ist, dann werden die zwei Bedingungen unterhalb als FALSCH ausgewertet, und die nächsten beiden als WAHR:

<lsl>(x && (x = 0) == 0 && x)</lsl>
<lsl>(x && (x = 0) == 0 && x == 0)</lsl>
<lsl>(x == 0 && (x = 0) == 0)</lsl>
<lsl>(x == 0 && (x = 0) == 0 && x)</lsl>

Beide Seiten werden ausgewertet, unabhängig davon ob eine der Seiten WAHR ist.

'''Anmerkung:''' Gleichheits-Test bei Listen vergleichen nicht deren Inhalte, sondern lediglich deren Länge.
{| {{Prettytable}}
|+
==+ Operator==
<code>ergebnis = links + rechts</code>
|-{{Hl2}}
!Linker Typ
!Rechter Typ
!Ergebnistyp
!Beschreibung
|-
|integer
|integer
|integer
|Addiert '''links''' und '''rechts'''
|-
|integer
|float
|float
|Addiert '''links''' und '''rechts'''
|-
|float
|integer
|float
|Addiert '''links''' und '''rechts'''
|-
|string
|string
|string
|Hängt '''rechts''' an das Ende von '''links''' an.
|-
|list
|*
|list
|Hängt '''rechts''' nach dem Ende von '''links''' an.
|-
|*
|list
|list
|Fügt '''links''' vor dem Start von '''rechts''' ein.
|-
|vector
|vector
|vector
|Addiert '''links''' und '''rechts'''
|-
|rotation
|rotation
|rotation
|Addiert '''links''' und '''rechts''' Nicht brauchbar um Rotationen zu kombinieren, stattdessen verwendet man die Operatoren [[#* Operator|*]] oder [[#/ Operator|/]].
|}

{| {{Prettytable}}
|+

==Operator-Abkürzungen==
Alternativen zum einfachen '=' Operator...
|-{{Hl2}}
!Einfacher Zuweisungsoperator
!Operator-Abkürzung (shorthand operator)
|-
|a = a + 1
|a += 1
|-
|a = a – 1
|a -= 1
|-
|a = a * (n+1)
|a *= (n+1)
|-
|a = a / (n+1)
|a /= (n+1)
|-
|a = a % b
|a %= b
|}

==[http://de.wikipedia.org/wiki/De_Morgansche_Gesetze De Morgansche Regeln]==
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Bitweise Gleichwertigkeiten
!UND
!ODER
|-
|| <code>~(a & b)</code> || <code>~a | ~b</code>
|-
|| <code>~a & ~b</code> || <code>~(a | b)</code>
|-
| colspan="2" |
|-
|| <code>a & ~b</code> || <code>~(~a | b)</code>
|-
|| <code>~(a & ~b)</code> || <code>~a | b</code>
|-
|}
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Boole'sche Gleichwertigkeiten
!UND
!ODER
|-
|| <code>!(a && b)</code> || <code>!a || !b</code>
|-
|| <code>!a && !b</code> || <code>!(a || b)</code>
|-
| colspan="2" |
|-
|| <code>a && !b</code> || <code>!(!a || b)</code>
|-
|| <code>!(a && !b)</code> || <code>!a || b</code>
|-
|}
Nach den De Morganschen Regeln (zeilenweise dargestellt), ist der Code in der '''UND'''-Spalte logisch äquivalent zum Code in der '''ODER'''-Spalte. '''a''' und '''b''' müssen nicht zwangsläufig Variablen sein, sondern können auch Ausdrücke sein. In speziellen Fällen kann man diese Gleichwertigkeiten anwenden, um komplexen Code vereinfacht darzustellen. Es ist wichtig diese zwei Tabellen nicht zu verwechseln wenn man sie anwendet. Die ersten beiden Zeilen stellen die De Morganschen Regeln dar wie postuliert, und die letzten beiden Zeilen bauen darauf auf.
{{LSLC/de|Operators}}{{LSLC/de|Flow Control}}{{LSLC/de}}

LSL Operators/de

2014-09-08T05:22:57Z

MartinRJ Fayray: /* + Operator */ added missing translation

{{Multi-lang}}
{{LSL Header/de}}
Operatoren sind Zeichen mit denen man Informationen aus Variablen auf vordefinierte Weise verarbeiten lassen kann. Eine (mathematische) Aktion kann auf eine oder zwei Operanden angewendet werden.
Ein einfaches Beispiel ist 1 + 2, wobei die Zahlen 1 und 2 die Operanden darstellen, und '''+''' ist der Operator.

{| bgcolor="#FFFFFF" border="1" cellspacing="2" cellpadding="6"
|- bgColor="#A7C1F2"
! Operator
! Beschreibung
! Anwendungsbeispiel
|-
| () || Klammern || a * (b + c)
|-
| [] || Eckige Klammern: Listen-Konstruktor || [a, 2, "this", 0.01]
|-
| (''type'') || Typkonvertierung || message = "Das Ergebnis lautet:" + (string) ergebnis;
|-
| ! ~ ++ -- || Logisches-NICHT, Bitweises-NICHT, Inkrement, Dekrement || counter++;
|-
| * / % || Multiplikations/Skalarprodukt, Division, Modulus/Kreuzprodukt || rest = (anzahl + 1)%5;
|-
| - || Substraktion || eins = 3 - 2;
|-
| + || Addition oder String-Verknüpfung || two = 1+1;
text = "Hello" + "World";
|-
| + || Konkatenation oder Zusammenführung von Listen || meineListe = [1, 2, 3] + [4, 5];
neueListe = alteListe + zusatzListe;
|-
| << >> || Links Shift, Rechts Shift || acht = 4 << 1;
|-
| < <= > >= || Kleiner Als, Kleiner Als oder Gleich,
Größer Als, Größer Als oder Gleich
|| istFalsch = (6 <= 4);
|-
| == != || Vergleich auf Gleichheit, Vergleich auf Ungleichheit || istFalsch = ("dies" == "das");
|-
| & || Bitweises UND || zero = 4 & 2;
four = 4 & 4;
|-
| ^ || Bitweises XOR || zero = 4 ^ 4;
six = 4 ^ 2;
|-
| <nowiki>|</nowiki> || Bitweises ODER || vier = 4 <nowiki>|</nowiki> 4;
six = 4 <nowiki>|</nowiki> 2;
|-
| <nowiki>||</nowiki> || Logisches ODER || istWahr = (FALSE <nowiki>||</nowiki> TRUE);
|-
| && ||Logisches UND || istFalsch = (FALSE && TRUE);
|-
| = += -= *= /= %= || Zuweisung || vier = 4;
|}

'''Anmerkung:''' Anders als in den meisten anderen Programmiersprachen die den C-Stil für '''&&''' und '''||''' Operatoren anwenden, werden '''beide''' Operanden '''immer''' ausgewertet. Zum Beispiel:

<lsl>if (TRUE || 1/0) llSay(PUBLIC_CHANNEL, "Aha!");</lsl>

führt zu einer Fehlermeldung, statt "Aha" auszugeben.

'''Anmerkung:''' Die ++ (Inkrement) und -- (Dekrement) - Operatoren wirken sich auf die Zahl entweder vor oder nach der Auswertung aus, je nachdem ob sie vor oder nach dieser Zahl stehen.

<lsl>integer count;
if(!(++count)) // Wird erhöht, und danach ausgewertet.
llSay(PUBLIC_CHANNEL, "Aha"); // Wird nicht ausgegeben.</lsl>

<lsl>integer count;
if(!(count++)) // Wird ausgewertet und danach erhöht.
llSay(PUBLIC_CHANNEL, "Aha"); // Wird ausgegeben.</lsl>

'''Anmerkung:''' Die Boole'schen Operatoren '''||''' und '''&&''' werden in der Auswertungs-Reihenfolge von LSL als gleichwertig angesehen.

'''Anmerkung:''' Die Auswertunsreihenfolge unterscheidet sich von der Auswertungsreihenfolge der meisten Programmiersprachen. Wenn der Wert von x im nachfolgenden Beispiel initial 1 ist, dann werden die zwei Bedingungen unterhalb als FALSCH ausgewertet, und die nächsten beiden als WAHR:

<lsl>(x && (x = 0) == 0 && x)</lsl>
<lsl>(x && (x = 0) == 0 && x == 0)</lsl>
<lsl>(x == 0 && (x = 0) == 0)</lsl>
<lsl>(x == 0 && (x = 0) == 0 && x)</lsl>

Beide Seiten werden ausgewertet, unabhängig davon ob eine der Seiten WAHR ist.

'''Anmerkung:''' Gleichheits-Test bei Listen vergleichen nicht deren Inhalte, sondern lediglich deren Länge.
{| {{Prettytable}}
|+
==+ Operator==
<code>ergebnis = links + rechts</code>
|-{{Hl2}}
!Linker Typ
!Rechter Typ
!Ergebnistyp
!Beschreibung
|-
|integer
|integer
|integer
|Addiert '''links''' und '''rechts'''
|-
|integer
|float
|float
|Addiert '''links''' und '''rechts'''
|-
|float
|integer
|float
|Addiert '''links''' und '''rechts'''
|-
|string
|string
|string
|Hängt '''rechts''' an das Ende von '''links''' an.
|-
|list
|*
|list
|Hängt '''rechts''' nach dem Ende von '''links''' an.
|-
|*
|list
|list
|Fügt '''links''' vor dem Start von '''rechts''' ein.
|-
|vector
|vector
|vector
|Addiert '''links''' und '''rechts'''
|-
|rotation
|rotation
|rotation
|Addiert '''links''' und '''rechts''' Nicht brauchbar um Rotationen zu kombinieren, stattdessen verwendet man die Operatoren [[#* Operator|*]] oder [[#/ Operator|/]].
|}

{| {{Prettytable}}
|+

==Operator-Abkürzungen==
Alternativen zum einfachen '=' Operator...
|-{{Hl2}}
!Einfacher Zuweisungsoperator
!Operator-Abkürzung (shorthand operator)
|-
|a = a + 1
|a += 1
|-
|a = a – 1
|a -= 1
|-
|a = a * (n+1)
|a *= (n+1)
|-
|a = a / (n+1)
|a /= (n+1)
|-
|a = a % b
|a %= b
|}

==[http://de.wikipedia.org/wiki/De_Morgansche_Gesetze De Morgansche Regeln]==
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Bitweise Gleichwertigkeiten
!UND
!ODER
|-
|| <code>~(a & b)</code> || <code>~a | ~b</code>
|-
|| <code>~a & ~b</code> || <code>~(a | b)</code>
|-
| colspan="2" |
|-
|| <code>a & ~b</code> || <code>~(~a | b)</code>
|-
|| <code>~(a & ~b)</code> || <code>~a | b</code>
|-
|}
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Boole'sche Gleichwertigkeiten
!UND
!ODER
|-
|| <code>!(a && b)</code> || <code>!a || !b</code>
|-
|| <code>!a && !b</code> || <code>!(a || b)</code>
|-
| colspan="2" |
|-
|| <code>a && !b</code> || <code>!(!a || b)</code>
|-
|| <code>!(a && !b)</code> || <code>!a || b</code>
|-
|}
Nach den De Morganschen Regeln (zeilenweise dargestellt), ist der Code in der '''UND'''-Spalte logisch equivalent zum Code in der '''ODER'''-Spalte. '''a''' und '''b''' müssen nicht zwangsläufig Variablen sein, sondern können auch Ausdrücke sein. In speziellen Fällen kann man diese Gleichwertigkeiten anwenden, um komplexen Code vereinfacht darzustellen. Es ist wichtig diese zwei Tabellen nicht zu verwechseln wenn man sie anwendet. Die ersten beiden Zeilen stellen die De Morganschen Regeln dar wie postuliert, und die letzten beiden Zeilen bauen darauf auf.
{{LSLC/de|Operators}}{{LSLC/de|Flow Control}}{{LSLC/de}}

LSL Operators/de

2014-09-08T05:22:17Z

MartinRJ Fayray: /* De Morgansche Regeln */ fixed a typo

{{Multi-lang}}
{{LSL Header/de}}
Operatoren sind Zeichen mit denen man Informationen aus Variablen auf vordefinierte Weise verarbeiten lassen kann. Eine (mathematische) Aktion kann auf eine oder zwei Operanden angewendet werden.
Ein einfaches Beispiel ist 1 + 2, wobei die Zahlen 1 und 2 die Operanden darstellen, und '''+''' ist der Operator.

{| bgcolor="#FFFFFF" border="1" cellspacing="2" cellpadding="6"
|- bgColor="#A7C1F2"
! Operator
! Beschreibung
! Anwendungsbeispiel
|-
| () || Klammern || a * (b + c)
|-
| [] || Eckige Klammern: Listen-Konstruktor || [a, 2, "this", 0.01]
|-
| (''type'') || Typkonvertierung || message = "Das Ergebnis lautet:" + (string) ergebnis;
|-
| ! ~ ++ -- || Logisches-NICHT, Bitweises-NICHT, Inkrement, Dekrement || counter++;
|-
| * / % || Multiplikations/Skalarprodukt, Division, Modulus/Kreuzprodukt || rest = (anzahl + 1)%5;
|-
| - || Substraktion || eins = 3 - 2;
|-
| + || Addition oder String-Verknüpfung || two = 1+1;
text = "Hello" + "World";
|-
| + || Konkatenation oder Zusammenführung von Listen || meineListe = [1, 2, 3] + [4, 5];
neueListe = alteListe + zusatzListe;
|-
| << >> || Links Shift, Rechts Shift || acht = 4 << 1;
|-
| < <= > >= || Kleiner Als, Kleiner Als oder Gleich,
Größer Als, Größer Als oder Gleich
|| istFalsch = (6 <= 4);
|-
| == != || Vergleich auf Gleichheit, Vergleich auf Ungleichheit || istFalsch = ("dies" == "das");
|-
| & || Bitweises UND || zero = 4 & 2;
four = 4 & 4;
|-
| ^ || Bitweises XOR || zero = 4 ^ 4;
six = 4 ^ 2;
|-
| <nowiki>|</nowiki> || Bitweises ODER || vier = 4 <nowiki>|</nowiki> 4;
six = 4 <nowiki>|</nowiki> 2;
|-
| <nowiki>||</nowiki> || Logisches ODER || istWahr = (FALSE <nowiki>||</nowiki> TRUE);
|-
| && ||Logisches UND || istFalsch = (FALSE && TRUE);
|-
| = += -= *= /= %= || Zuweisung || vier = 4;
|}

'''Anmerkung:''' Anders als in den meisten anderen Programmiersprachen die den C-Stil für '''&&''' und '''||''' Operatoren anwenden, werden '''beide''' Operanden '''immer''' ausgewertet. Zum Beispiel:

<lsl>if (TRUE || 1/0) llSay(PUBLIC_CHANNEL, "Aha!");</lsl>

führt zu einer Fehlermeldung, statt "Aha" auszugeben.

'''Anmerkung:''' Die ++ (Inkrement) und -- (Dekrement) - Operatoren wirken sich auf die Zahl entweder vor oder nach der Auswertung aus, je nachdem ob sie vor oder nach dieser Zahl stehen.

<lsl>integer count;
if(!(++count)) // Wird erhöht, und danach ausgewertet.
llSay(PUBLIC_CHANNEL, "Aha"); // Wird nicht ausgegeben.</lsl>

<lsl>integer count;
if(!(count++)) // Wird ausgewertet und danach erhöht.
llSay(PUBLIC_CHANNEL, "Aha"); // Wird ausgegeben.</lsl>

'''Anmerkung:''' Die Boole'schen Operatoren '''||''' und '''&&''' werden in der Auswertungs-Reihenfolge von LSL als gleichwertig angesehen.

'''Anmerkung:''' Die Auswertunsreihenfolge unterscheidet sich von der Auswertungsreihenfolge der meisten Programmiersprachen. Wenn der Wert von x im nachfolgenden Beispiel initial 1 ist, dann werden die zwei Bedingungen unterhalb als FALSCH ausgewertet, und die nächsten beiden als WAHR:

<lsl>(x && (x = 0) == 0 && x)</lsl>
<lsl>(x && (x = 0) == 0 && x == 0)</lsl>
<lsl>(x == 0 && (x = 0) == 0)</lsl>
<lsl>(x == 0 && (x = 0) == 0 && x)</lsl>

Beide Seiten werden ausgewertet, unabhängig davon ob eine der Seiten WAHR ist.

'''Anmerkung:''' Gleichheits-Test bei Listen vergleichen nicht deren Inhalte, sondern lediglich deren Länge.
{| {{Prettytable}}
|+
==+ Operator==
<code>result = left + right</code>
|-{{Hl2}}
!Linker Typ
!Rechter Typ
!Ergebnistyp
!Beschreibung
|-
|integer
|integer
|integer
|Addiert '''links''' und '''rechts'''
|-
|integer
|float
|float
|Addiert '''links''' und '''rechts'''
|-
|float
|integer
|float
|Addiert '''links''' und '''rechts'''
|-
|string
|string
|string
|Hängt '''rechts''' an das Ende von '''links''' an.
|-
|list
|*
|list
|Hängt '''rechts''' nach dem Ende von '''links''' an.
|-
|*
|list
|list
|Fügt '''links''' vor dem Start von '''rechts''' ein.
|-
|vector
|vector
|vector
|Addiert '''links''' und '''rechts'''
|-
|rotation
|rotation
|rotation
|Addiert '''links''' und '''rechts''' Nicht brauchbar um Rotationen zu kombinieren, stattdessen verwendet man die Operatoren [[#* Operator|*]] oder [[#/ Operator|/]].
|}

{| {{Prettytable}}
|+
==Operator-Abkürzungen==
Alternativen zum einfachen '=' Operator...
|-{{Hl2}}
!Einfacher Zuweisungsoperator
!Operator-Abkürzung (shorthand operator)
|-
|a = a + 1
|a += 1
|-
|a = a – 1
|a -= 1
|-
|a = a * (n+1)
|a *= (n+1)
|-
|a = a / (n+1)
|a /= (n+1)
|-
|a = a % b
|a %= b
|}

==[http://de.wikipedia.org/wiki/De_Morgansche_Gesetze De Morgansche Regeln]==
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Bitweise Gleichwertigkeiten
!UND
!ODER
|-
|| <code>~(a & b)</code> || <code>~a | ~b</code>
|-
|| <code>~a & ~b</code> || <code>~(a | b)</code>
|-
| colspan="2" |
|-
|| <code>a & ~b</code> || <code>~(~a | b)</code>
|-
|| <code>~(a & ~b)</code> || <code>~a | b</code>
|-
|}
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Boole'sche Gleichwertigkeiten
!UND
!ODER
|-
|| <code>!(a && b)</code> || <code>!a || !b</code>
|-
|| <code>!a && !b</code> || <code>!(a || b)</code>
|-
| colspan="2" |
|-
|| <code>a && !b</code> || <code>!(!a || b)</code>
|-
|| <code>!(a && !b)</code> || <code>!a || b</code>
|-
|}
Nach den De Morganschen Regeln (zeilenweise dargestellt), ist der Code in der '''UND'''-Spalte logisch equivalent zum Code in der '''ODER'''-Spalte. '''a''' und '''b''' müssen nicht zwangsläufig Variablen sein, sondern können auch Ausdrücke sein. In speziellen Fällen kann man diese Gleichwertigkeiten anwenden, um komplexen Code vereinfacht darzustellen. Es ist wichtig diese zwei Tabellen nicht zu verwechseln wenn man sie anwendet. Die ersten beiden Zeilen stellen die De Morganschen Regeln dar wie postuliert, und die letzten beiden Zeilen bauen darauf auf.
{{LSLC/de|Operators}}{{LSLC/de|Flow Control}}{{LSLC/de}}

LSL Operators/de

2014-09-08T05:21:38Z

MartinRJ Fayray: /* {{Wikipedia|De Morgan's Gesetze|w=n}} */ wikipedia link in section's title didn't work bec. it linked to English wikipedia, so I changed it

{{Multi-lang}}
{{LSL Header/de}}
Operatoren sind Zeichen mit denen man Informationen aus Variablen auf vordefinierte Weise verarbeiten lassen kann. Eine (mathematische) Aktion kann auf eine oder zwei Operanden angewendet werden.
Ein einfaches Beispiel ist 1 + 2, wobei die Zahlen 1 und 2 die Operanden darstellen, und '''+''' ist der Operator.

{| bgcolor="#FFFFFF" border="1" cellspacing="2" cellpadding="6"
|- bgColor="#A7C1F2"
! Operator
! Beschreibung
! Anwendungsbeispiel
|-
| () || Klammern || a * (b + c)
|-
| [] || Eckige Klammern: Listen-Konstruktor || [a, 2, "this", 0.01]
|-
| (''type'') || Typkonvertierung || message = "Das Ergebnis lautet:" + (string) ergebnis;
|-
| ! ~ ++ -- || Logisches-NICHT, Bitweises-NICHT, Inkrement, Dekrement || counter++;
|-
| * / % || Multiplikations/Skalarprodukt, Division, Modulus/Kreuzprodukt || rest = (anzahl + 1)%5;
|-
| - || Substraktion || eins = 3 - 2;
|-
| + || Addition oder String-Verknüpfung || two = 1+1;
text = "Hello" + "World";
|-
| + || Konkatenation oder Zusammenführung von Listen || meineListe = [1, 2, 3] + [4, 5];
neueListe = alteListe + zusatzListe;
|-
| << >> || Links Shift, Rechts Shift || acht = 4 << 1;
|-
| < <= > >= || Kleiner Als, Kleiner Als oder Gleich,
Größer Als, Größer Als oder Gleich
|| istFalsch = (6 <= 4);
|-
| == != || Vergleich auf Gleichheit, Vergleich auf Ungleichheit || istFalsch = ("dies" == "das");
|-
| & || Bitweises UND || zero = 4 & 2;
four = 4 & 4;
|-
| ^ || Bitweises XOR || zero = 4 ^ 4;
six = 4 ^ 2;
|-
| <nowiki>|</nowiki> || Bitweises ODER || vier = 4 <nowiki>|</nowiki> 4;
six = 4 <nowiki>|</nowiki> 2;
|-
| <nowiki>||</nowiki> || Logisches ODER || istWahr = (FALSE <nowiki>||</nowiki> TRUE);
|-
| && ||Logisches UND || istFalsch = (FALSE && TRUE);
|-
| = += -= *= /= %= || Zuweisung || vier = 4;
|}

'''Anmerkung:''' Anders als in den meisten anderen Programmiersprachen die den C-Stil für '''&&''' und '''||''' Operatoren anwenden, werden '''beide''' Operanden '''immer''' ausgewertet. Zum Beispiel:

<lsl>if (TRUE || 1/0) llSay(PUBLIC_CHANNEL, "Aha!");</lsl>

führt zu einer Fehlermeldung, statt "Aha" auszugeben.

'''Anmerkung:''' Die ++ (Inkrement) und -- (Dekrement) - Operatoren wirken sich auf die Zahl entweder vor oder nach der Auswertung aus, je nachdem ob sie vor oder nach dieser Zahl stehen.

<lsl>integer count;
if(!(++count)) // Wird erhöht, und danach ausgewertet.
llSay(PUBLIC_CHANNEL, "Aha"); // Wird nicht ausgegeben.</lsl>

<lsl>integer count;
if(!(count++)) // Wird ausgewertet und danach erhöht.
llSay(PUBLIC_CHANNEL, "Aha"); // Wird ausgegeben.</lsl>

'''Anmerkung:''' Die Boole'schen Operatoren '''||''' und '''&&''' werden in der Auswertungs-Reihenfolge von LSL als gleichwertig angesehen.

'''Anmerkung:''' Die Auswertunsreihenfolge unterscheidet sich von der Auswertungsreihenfolge der meisten Programmiersprachen. Wenn der Wert von x im nachfolgenden Beispiel initial 1 ist, dann werden die zwei Bedingungen unterhalb als FALSCH ausgewertet, und die nächsten beiden als WAHR:

<lsl>(x && (x = 0) == 0 && x)</lsl>
<lsl>(x && (x = 0) == 0 && x == 0)</lsl>
<lsl>(x == 0 && (x = 0) == 0)</lsl>
<lsl>(x == 0 && (x = 0) == 0 && x)</lsl>

Beide Seiten werden ausgewertet, unabhängig davon ob eine der Seiten WAHR ist.

'''Anmerkung:''' Gleichheits-Test bei Listen vergleichen nicht deren Inhalte, sondern lediglich deren Länge.
{| {{Prettytable}}
|+
==+ Operator==
<code>result = left + right</code>
|-{{Hl2}}
!Linker Typ
!Rechter Typ
!Ergebnistyp
!Beschreibung
|-
|integer
|integer
|integer
|Addiert '''links''' und '''rechts'''
|-
|integer
|float
|float
|Addiert '''links''' und '''rechts'''
|-
|float
|integer
|float
|Addiert '''links''' und '''rechts'''
|-
|string
|string
|string
|Hängt '''rechts''' an das Ende von '''links''' an.
|-
|list
|*
|list
|Hängt '''rechts''' nach dem Ende von '''links''' an.
|-
|*
|list
|list
|Fügt '''links''' vor dem Start von '''rechts''' ein.
|-
|vector
|vector
|vector
|Addiert '''links''' und '''rechts'''
|-
|rotation
|rotation
|rotation
|Addiert '''links''' und '''rechts''' Nicht brauchbar um Rotationen zu kombinieren, stattdessen verwendet man die Operatoren [[#* Operator|*]] oder [[#/ Operator|/]].
|}

{| {{Prettytable}}
|+
==Operator-Abkürzungen==
Alternativen zum einfachen '=' Operator...
|-{{Hl2}}
!Einfacher Zuweisungsoperator
!Operator-Abkürzung (shorthand operator)
|-
|a = a + 1
|a += 1
|-
|a = a – 1
|a -= 1
|-
|a = a * (n+1)
|a *= (n+1)
|-
|a = a / (n+1)
|a /= (n+1)
|-
|a = a % b
|a %= b
|}

==[http://de.wikipedia.org/wiki/De_Morgansche_Gesetze De Morgansche Regeln]==
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Bitweise Gleichwertigkeiten
!UND
!ODER
|-
|| <code>~(a & b)</code> || <code>~a | ~b</code>
|-
|| <code>~a & ~b</code> || <code>~(a | b)</code>
|-
| colspan="2" |
|-
|| <code>a & ~b</code> || <code>~(~a | b)</code>
|-
|| <code>~(a & ~b)</code> || <code>~a | b</code>
|-
|}
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Boole'sche Gleichwertigkeiten
!UND
!ODER
|-
|| <code>!(a && b)</code> || <code>!a || !b</code>
|-
|| <code>!a && !b</code> || <code>!(a || b)</code>
|-
| colspan="2" |
|-
|| <code>a && !b</code> || <code>!(!a || b)</code>
|-
|| <code>!(a && !b)</code> || <code>!a || b</code>
|-
|}
Nach den De Morganschen Regeln (zeilenweise dargestellt), ist der Code in der '''UND''' Spalte logisch equivalent zum Code ind er '''ODER'''. '''a''' und '''b''' müssen nicht zwangsläufig Variablen sein, sondern können auch Ausdrücke sein. In speziellen Fällen kann man diese Gleichwertigkeiten anwenden, um komplexen Code vereinfacht darzustellen. Es ist wichtig diese zwei Tabellen nicht zu verwechseln wenn man sie anwendet. Die ersten beiden Zeilen stellen die De Morganschen Regeln dar wie postuliert, und die letzten beiden Zeilen bauen darauf auf.
{{LSLC/de|Operators}}{{LSLC/de|Flow Control}}{{LSLC/de}}

LSL Operators/de

2014-09-08T05:20:24Z

MartinRJ Fayray: /* {{Wikipedia|De Morgan's Gesetze|w=n}} */ wikipedia link didn't work bec. it linked to English wikipedia, so I removed it

{{Multi-lang}}
{{LSL Header/de}}
Operatoren sind Zeichen mit denen man Informationen aus Variablen auf vordefinierte Weise verarbeiten lassen kann. Eine (mathematische) Aktion kann auf eine oder zwei Operanden angewendet werden.
Ein einfaches Beispiel ist 1 + 2, wobei die Zahlen 1 und 2 die Operanden darstellen, und '''+''' ist der Operator.

{| bgcolor="#FFFFFF" border="1" cellspacing="2" cellpadding="6"
|- bgColor="#A7C1F2"
! Operator
! Beschreibung
! Anwendungsbeispiel
|-
| () || Klammern || a * (b + c)
|-
| [] || Eckige Klammern: Listen-Konstruktor || [a, 2, "this", 0.01]
|-
| (''type'') || Typkonvertierung || message = "Das Ergebnis lautet:" + (string) ergebnis;
|-
| ! ~ ++ -- || Logisches-NICHT, Bitweises-NICHT, Inkrement, Dekrement || counter++;
|-
| * / % || Multiplikations/Skalarprodukt, Division, Modulus/Kreuzprodukt || rest = (anzahl + 1)%5;
|-
| - || Substraktion || eins = 3 - 2;
|-
| + || Addition oder String-Verknüpfung || two = 1+1;
text = "Hello" + "World";
|-
| + || Konkatenation oder Zusammenführung von Listen || meineListe = [1, 2, 3] + [4, 5];
neueListe = alteListe + zusatzListe;
|-
| << >> || Links Shift, Rechts Shift || acht = 4 << 1;
|-
| < <= > >= || Kleiner Als, Kleiner Als oder Gleich,
Größer Als, Größer Als oder Gleich
|| istFalsch = (6 <= 4);
|-
| == != || Vergleich auf Gleichheit, Vergleich auf Ungleichheit || istFalsch = ("dies" == "das");
|-
| & || Bitweises UND || zero = 4 & 2;
four = 4 & 4;
|-
| ^ || Bitweises XOR || zero = 4 ^ 4;
six = 4 ^ 2;
|-
| <nowiki>|</nowiki> || Bitweises ODER || vier = 4 <nowiki>|</nowiki> 4;
six = 4 <nowiki>|</nowiki> 2;
|-
| <nowiki>||</nowiki> || Logisches ODER || istWahr = (FALSE <nowiki>||</nowiki> TRUE);
|-
| && ||Logisches UND || istFalsch = (FALSE && TRUE);
|-
| = += -= *= /= %= || Zuweisung || vier = 4;
|}

'''Anmerkung:''' Anders als in den meisten anderen Programmiersprachen die den C-Stil für '''&&''' und '''||''' Operatoren anwenden, werden '''beide''' Operanden '''immer''' ausgewertet. Zum Beispiel:

<lsl>if (TRUE || 1/0) llSay(PUBLIC_CHANNEL, "Aha!");</lsl>

führt zu einer Fehlermeldung, statt "Aha" auszugeben.

'''Anmerkung:''' Die ++ (Inkrement) und -- (Dekrement) - Operatoren wirken sich auf die Zahl entweder vor oder nach der Auswertung aus, je nachdem ob sie vor oder nach dieser Zahl stehen.

<lsl>integer count;
if(!(++count)) // Wird erhöht, und danach ausgewertet.
llSay(PUBLIC_CHANNEL, "Aha"); // Wird nicht ausgegeben.</lsl>

<lsl>integer count;
if(!(count++)) // Wird ausgewertet und danach erhöht.
llSay(PUBLIC_CHANNEL, "Aha"); // Wird ausgegeben.</lsl>

'''Anmerkung:''' Die Boole'schen Operatoren '''||''' und '''&&''' werden in der Auswertungs-Reihenfolge von LSL als gleichwertig angesehen.

'''Anmerkung:''' Die Auswertunsreihenfolge unterscheidet sich von der Auswertungsreihenfolge der meisten Programmiersprachen. Wenn der Wert von x im nachfolgenden Beispiel initial 1 ist, dann werden die zwei Bedingungen unterhalb als FALSCH ausgewertet, und die nächsten beiden als WAHR:

<lsl>(x && (x = 0) == 0 && x)</lsl>
<lsl>(x && (x = 0) == 0 && x == 0)</lsl>
<lsl>(x == 0 && (x = 0) == 0)</lsl>
<lsl>(x == 0 && (x = 0) == 0 && x)</lsl>

Beide Seiten werden ausgewertet, unabhängig davon ob eine der Seiten WAHR ist.

'''Anmerkung:''' Gleichheits-Test bei Listen vergleichen nicht deren Inhalte, sondern lediglich deren Länge.
{| {{Prettytable}}
|+
==+ Operator==
<code>result = left + right</code>
|-{{Hl2}}
!Linker Typ
!Rechter Typ
!Ergebnistyp
!Beschreibung
|-
|integer
|integer
|integer
|Addiert '''links''' und '''rechts'''
|-
|integer
|float
|float
|Addiert '''links''' und '''rechts'''
|-
|float
|integer
|float
|Addiert '''links''' und '''rechts'''
|-
|string
|string
|string
|Hängt '''rechts''' an das Ende von '''links''' an.
|-
|list
|*
|list
|Hängt '''rechts''' nach dem Ende von '''links''' an.
|-
|*
|list
|list
|Fügt '''links''' vor dem Start von '''rechts''' ein.
|-
|vector
|vector
|vector
|Addiert '''links''' und '''rechts'''
|-
|rotation
|rotation
|rotation
|Addiert '''links''' und '''rechts''' Nicht brauchbar um Rotationen zu kombinieren, stattdessen verwendet man die Operatoren [[#* Operator|*]] oder [[#/ Operator|/]].
|}

{| {{Prettytable}}
|+
==Operator-Abkürzungen==
Alternativen zum einfachen '=' Operator...
|-{{Hl2}}
!Einfacher Zuweisungsoperator
!Operator-Abkürzung (shorthand operator)
|-
|a = a + 1
|a += 1
|-
|a = a – 1
|a -= 1
|-
|a = a * (n+1)
|a *= (n+1)
|-
|a = a / (n+1)
|a /= (n+1)
|-
|a = a % b
|a %= b
|}

=={{Wikipedia|De Morgan's Gesetze|w=n}}==
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Bitweise Gleichwertigkeiten
!UND
!ODER
|-
|| <code>~(a & b)</code> || <code>~a | ~b</code>
|-
|| <code>~a & ~b</code> || <code>~(a | b)</code>
|-
| colspan="2" |
|-
|| <code>a & ~b</code> || <code>~(~a | b)</code>
|-
|| <code>~(a & ~b)</code> || <code>~a | b</code>
|-
|}
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Boole'sche Gleichwertigkeiten
!UND
!ODER
|-
|| <code>!(a && b)</code> || <code>!a || !b</code>
|-
|| <code>!a && !b</code> || <code>!(a || b)</code>
|-
| colspan="2" |
|-
|| <code>a && !b</code> || <code>!(!a || b)</code>
|-
|| <code>!(a && !b)</code> || <code>!a || b</code>
|-
|}
Nach den De Morganschen Regeln (zeilenweise dargestellt), ist der Code in der '''UND''' Spalte logisch equivalent zum Code ind er '''ODER'''. '''a''' und '''b''' müssen nicht zwangsläufig Variablen sein, sondern können auch Ausdrücke sein. In speziellen Fällen kann man diese Gleichwertigkeiten anwenden, um komplexen Code vereinfacht darzustellen. Es ist wichtig diese zwei Tabellen nicht zu verwechseln wenn man sie anwendet. Die ersten beiden Zeilen stellen die De Morganschen Regeln dar wie postuliert, und die letzten beiden Zeilen bauen darauf auf.
{{LSLC/de|Operators}}{{LSLC/de|Flow Control}}{{LSLC/de}}

LSL Operators/de

2014-09-08T05:14:58Z

MartinRJ Fayray: First translation from English

{{Multi-lang}}
{{LSL Header/de}}
Operatoren sind Zeichen mit denen man Informationen aus Variablen auf vordefinierte Weise verarbeiten lassen kann. Eine (mathematische) Aktion kann auf eine oder zwei Operanden angewendet werden.
Ein einfaches Beispiel ist 1 + 2, wobei die Zahlen 1 und 2 die Operanden darstellen, und '''+''' ist der Operator.

{| bgcolor="#FFFFFF" border="1" cellspacing="2" cellpadding="6"
|- bgColor="#A7C1F2"
! Operator
! Beschreibung
! Anwendungsbeispiel
|-
| () || Klammern || a * (b + c)
|-
| [] || Eckige Klammern: Listen-Konstruktor || [a, 2, "this", 0.01]
|-
| (''type'') || Typkonvertierung || message = "Das Ergebnis lautet:" + (string) ergebnis;
|-
| ! ~ ++ -- || Logisches-NICHT, Bitweises-NICHT, Inkrement, Dekrement || counter++;
|-
| * / % || Multiplikations/Skalarprodukt, Division, Modulus/Kreuzprodukt || rest = (anzahl + 1)%5;
|-
| - || Substraktion || eins = 3 - 2;
|-
| + || Addition oder String-Verknüpfung || two = 1+1;
text = "Hello" + "World";
|-
| + || Konkatenation oder Zusammenführung von Listen || meineListe = [1, 2, 3] + [4, 5];
neueListe = alteListe + zusatzListe;
|-
| << >> || Links Shift, Rechts Shift || acht = 4 << 1;
|-
| < <= > >= || Kleiner Als, Kleiner Als oder Gleich,
Größer Als, Größer Als oder Gleich
|| istFalsch = (6 <= 4);
|-
| == != || Vergleich auf Gleichheit, Vergleich auf Ungleichheit || istFalsch = ("dies" == "das");
|-
| & || Bitweises UND || zero = 4 & 2;
four = 4 & 4;
|-
| ^ || Bitweises XOR || zero = 4 ^ 4;
six = 4 ^ 2;
|-
| <nowiki>|</nowiki> || Bitweises ODER || vier = 4 <nowiki>|</nowiki> 4;
six = 4 <nowiki>|</nowiki> 2;
|-
| <nowiki>||</nowiki> || Logisches ODER || istWahr = (FALSE <nowiki>||</nowiki> TRUE);
|-
| && ||Logisches UND || istFalsch = (FALSE && TRUE);
|-
| = += -= *= /= %= || Zuweisung || vier = 4;
|}

'''Anmerkung:''' Anders als in den meisten anderen Programmiersprachen die den C-Stil für '''&&''' und '''||''' Operatoren anwenden, werden '''beide''' Operanden '''immer''' ausgewertet. Zum Beispiel:

<lsl>if (TRUE || 1/0) llSay(PUBLIC_CHANNEL, "Aha!");</lsl>

führt zu einer Fehlermeldung, statt "Aha" auszugeben.

'''Anmerkung:''' Die ++ (Inkrement) und -- (Dekrement) - Operatoren wirken sich auf die Zahl entweder vor oder nach der Auswertung aus, je nachdem ob sie vor oder nach dieser Zahl stehen.

<lsl>integer count;
if(!(++count)) // Wird erhöht, und danach ausgewertet.
llSay(PUBLIC_CHANNEL, "Aha"); // Wird nicht ausgegeben.</lsl>

<lsl>integer count;
if(!(count++)) // Wird ausgewertet und danach erhöht.
llSay(PUBLIC_CHANNEL, "Aha"); // Wird ausgegeben.</lsl>

'''Anmerkung:''' Die Boole'schen Operatoren '''||''' und '''&&''' werden in der Auswertungs-Reihenfolge von LSL als gleichwertig angesehen.

'''Anmerkung:''' Die Auswertunsreihenfolge unterscheidet sich von der Auswertungsreihenfolge der meisten Programmiersprachen. Wenn der Wert von x im nachfolgenden Beispiel initial 1 ist, dann werden die zwei Bedingungen unterhalb als FALSCH ausgewertet, und die nächsten beiden als WAHR:

<lsl>(x && (x = 0) == 0 && x)</lsl>
<lsl>(x && (x = 0) == 0 && x == 0)</lsl>
<lsl>(x == 0 && (x = 0) == 0)</lsl>
<lsl>(x == 0 && (x = 0) == 0 && x)</lsl>

Beide Seiten werden ausgewertet, unabhängig davon ob eine der Seiten WAHR ist.

'''Anmerkung:''' Gleichheits-Test bei Listen vergleichen nicht deren Inhalte, sondern lediglich deren Länge.
{| {{Prettytable}}
|+
==+ Operator==
<code>result = left + right</code>
|-{{Hl2}}
!Linker Typ
!Rechter Typ
!Ergebnistyp
!Beschreibung
|-
|integer
|integer
|integer
|Addiert '''links''' und '''rechts'''
|-
|integer
|float
|float
|Addiert '''links''' und '''rechts'''
|-
|float
|integer
|float
|Addiert '''links''' und '''rechts'''
|-
|string
|string
|string
|Hängt '''rechts''' an das Ende von '''links''' an.
|-
|list
|*
|list
|Hängt '''rechts''' nach dem Ende von '''links''' an.
|-
|*
|list
|list
|Fügt '''links''' vor dem Start von '''rechts''' ein.
|-
|vector
|vector
|vector
|Addiert '''links''' und '''rechts'''
|-
|rotation
|rotation
|rotation
|Addiert '''links''' und '''rechts''' Nicht brauchbar um Rotationen zu kombinieren, stattdessen verwendet man die Operatoren [[#* Operator|*]] oder [[#/ Operator|/]].
|}

{| {{Prettytable}}
|+
==Operator-Abkürzungen==
Alternativen zum einfachen '=' Operator...
|-{{Hl2}}
!Einfacher Zuweisungsoperator
!Operator-Abkürzung (shorthand operator)
|-
|a = a + 1
|a += 1
|-
|a = a – 1
|a -= 1
|-
|a = a * (n+1)
|a *= (n+1)
|-
|a = a / (n+1)
|a /= (n+1)
|-
|a = a % b
|a %= b
|}

=={{Wikipedia|De Morgan's Gesetze|w=n}}==
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Bitweise Gleichwertigkeiten
!UND
!ODER
|-
|| <code>~(a & b)</code> || <code>~a | ~b</code>
|-
|| <code>~a & ~b</code> || <code>~(a | b)</code>
|-
| colspan="2" |
|-
|| <code>a & ~b</code> || <code>~(~a | b)</code>
|-
|| <code>~(a & ~b)</code> || <code>~a | b</code>
|-
|}
{| {{Prettytable|style=margin-top:0; float:left;}}
|+ Boole'sche Gleichwertigkeiten
!UND
!ODER
|-
|| <code>!(a && b)</code> || <code>!a || !b</code>
|-
|| <code>!a && !b</code> || <code>!(a || b)</code>
|-
| colspan="2" |
|-
|| <code>a && !b</code> || <code>!(!a || b)</code>
|-
|| <code>!(a && !b)</code> || <code>!a || b</code>
|-
|}
Nach {{Wikipedia|De Morgan's Gesetze|w=n}} (zeilenweise dargestellt), ist der Code in der '''UND''' Spalte logisch equivalent zum Code ind er '''ODER'''. '''a''' und '''b''' müssen nicht zwangsläufig Variablen sein, sondern können auch Ausdrücke sein. In speziellen Fällen kann man diese Gleichwertigkeiten anwenden, um komplexen Code vereinfacht darzustellen. Es ist wichtig diese zwei Tabellen nicht zu verwechseln wenn man sie anwendet. Die ersten beiden Zeilen stellen De Morgan's Gesetze dar wie postuliert, und die letzten beiden Zeilen bauen darauf auf.
{{LSLC/de|Operators}}{{LSLC/de|Flow Control}}{{LSLC/de}}

Verwendung von JSON in LSL

2014-02-19T12:11:46Z

MartinRJ Fayray: Added reference to English wiki-page for information about 'specifiers'.

{{LSL Header/de|mlr=Json usage in LSL}}{{LSLC/de}}{{LSLC/de|JSON|*Verwendung von JSON in LSL}}
==Übersicht==
[http://www.json.org/ JSON] (JavaScript Object Notation) ist ein Textformat (unabhängig von Programmiersprache und Architektur) um [http://de.wikipedia.org/wiki/Serialisierung Datenstrukturen zu serialisieren], ähnlich wie es [http://de.wikipedia.org/wiki/XML XML] für Dokumente macht, aber in einer wesentlich kompakteren Form.
Es wird in der einfachsten Form als ein reiner String dargestellt, der in seinem Aufbau einem [http://tools.ietf.org/html/rfc4627 Regelset] folgt.
Diese Regeln erlauben die Codierung, Manipulation, Speicherung, Übermittlung und Decodierung von komplexen Datenstrukturen in einer kurzen, lesbaren Form.
Json-Text kann man benutzen, um zwischen JSON-kompatiblen Anwendungen zu kommunizieren, und wird in erster Linie für die Webclient-Server-Kommunikation verwendet.

JSON ermöglicht es [http://de.wikipedia.org/wiki/Objekt_%28Programmierung%29 Objekte], [http://de.wikipedia.org/wiki/Datenbank Datenbanken] und komplexe und abstrakte Datentypen zu erzeugen ([http://de.wikipedia.org/wiki/Feld_%28Datentyp%29 multidimensionale und assoziative Arrays], [http://de.wikipedia.org/wiki/Last_In_%E2%80%93_First_Out Stacks], [http://de.wikipedia.org/wiki/First_In_%E2%80%93_First_Out Queues] und [http://de.wikipedia.org/wiki/Liste_%28Datenstruktur%29 Listen]).

Da LSL diese Datentypen nicht unterstützt, werden zur Anwendung dieser Datentypen user-generierte Funktionen benötigt (z.B. getAllKeys(), getArrayLength(), deleteItem(), und Iterator-Operatoren),
um von den Vorteilen (wie Datenkapselung, Speicher-Einsparung für lange Listen, Verschachtelung von vermischten Datenstrukturen) die JSON ermöglichen, profitieren zu können.

Ein LSL-basiertes Testskript für diese Funktionen kann man hier abrufen: [[Json_usage_in_LSL/TestScript]].

==Typenkonvertierung==

Siehe [[llJsonValueType{{#var:lang}}|llJsonValueType]]

==Neue LSL Funktionen==

*[[LlJson2List{{#var:lang}}|LlJson2List]]
*[[LlJsonGetValue{{#var:lang}}|LlJsonGetValue]]
*[[LlJsonSetValue{{#var:lang}}|LlJsonSetValue]]
*[[LlJsonValueType{{#var:lang}}|LlJsonValueType]]
*[[LlList2Json{{#var:lang}}|LlList2Json]]

'''''HINWEIS''''' Bitte besuchen Sie auch die originale Englische Version dieser Seite für weitere Informationen, wie Beispielskripts etc.: [[Json_usage_in_LSL]] - besonders für Informationen über die Verwendung der '''Spezifizierer'''.

User talk:Kireji Haiku

2014-01-12T05:25:54Z

MartinRJ Fayray: /* JSON /de pages */ -- signature

== Unnecessary Edits ==

Kindly desist from your inane paranoid obsession with a personal fad. Strife and I have discussed the purpose of edits and agree that edits should not unnecessarily change the style chosen by the example code originators. And don't split hairs with me about what constitutes "style". I will continue to revert unneeded edits back to what the originator intended. [[User:Omei Qunhua|Omei Qunhua]] 07:13, 31 December 2013 (PST)

I obviously have not explained myself simply or clearly enough. Let's try again. There have been thousands of scripts contributed to this Wiki, by hundreds if not thousands of contributors. There have apparently been a million scripts written in LSL and there are tens of thousands of scripts in public libraries. You, I believe, are almost alone among this vast horde of experience in insisting on PUBLIC_CHANNEL and ERROR_GENERIC, (float) FALSE etc. That places you a minuscule minority. You have NO RIGHT to impose your most exceptional view on the rest of us. I personally consider it OBSCENE that you dare to suggest my contributions are in error sufficiently to warrant you getting your sticky little fingers on them, just because I didn't adhere to a very individual quirk of yours in my otherwise totally correct script. What on earth do you think gives you this right? I am sure you are ABSOLUTELY convinced of the advantages of your preferences. By all means feel free to exercise your preferences in your own creations, and I will honour your right to write what you wish in your own creations, so long as they are accurate (i.e. compile and produce correct results). But that does not give you the right as one individual to impose your ways on thousands of the rest of us. The way to convince others is not to trample rough-shod over years of work by the dedicated majority. That only alienates you, certainly from me. I repeat, I will continue to try and ensure that the valid preferences of script originators are preserved. What's your excuse? [[User:Omei Qunhua|Omei Qunhua]] 09:43, 31 December 2013 (PST)

== JSON_APPEND and JSON_DELETE ==

I can't get on right now to test this but what happens if you use [[JSON_APPEND]] with [[JSON_DELETE]]? If the world were a wonderful place it would delete the last value.
<lsl>llOwnerSay(llJsonSetValue("[0,1]", [JSON_APPEND], JSON_DELETE));</lsl>
--'''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 06:19, 4 October 2013 (PDT)

:What do you think happens if it's NOT an array?
:<lsl>llOwnerSay(llJsonSetValue("{a:1}", [JSON_APPEND], JSON_DELETE));</lsl>
:-- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 06:23, 4 October 2013 (PDT)

::They both output [[JSON_INVALID]]. I'll erm... test and see if there's a better example script :P -- [[User:Kireji Haiku|Kireji Haiku]] 06:29, 4 October 2013 (PDT)

:::JSON_DELETE I think is still only in RC. Thanks for looking into this. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 06:32, 4 October 2013 (PDT)

:::I think I'll just make a feature suggestion for JSON_LAST so there is no ambiguity. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 06:35, 4 October 2013 (PDT)

::::I tested both on <code>LeTigre Sandbox 1</code> which runs <code>3.6.7.281331</code>. It seems that is before the one introducing [[JSON_DELETE]]. So yeah... will wait and see. I removed the example script for now. -- [[User:Kireji Haiku|Kireji Haiku]] 06:39, 4 October 2013 (PDT)

:::::<.< sorry for wasting your time. [[JSON_LAST]] = {{JIRA|BUG-4075}} -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 06:47, 4 October 2013 (PDT)

:::::Thanks for the useless link. I'd have taken a look, but no perms. So I'll just hope someone will react to that. Not that anybody would to then ones I report. Have a nice one ;) -- [[User:Kireji Haiku|Kireji Haiku]] 06:54, 4 October 2013 (PDT)

:::::: ^^; sorry -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 07:05, 4 October 2013 (PDT)

:::::::Nah, it's all good. I just don't like the way some of the Linden Lab staff reacts to user reports by first acknowledging bugs and then ignoring any help provided to actually get them fixed. Closing down the JIRA from the public doesn't help either. Anyhow, I'll stop rambling off-topic. Cya -- [[User:Kireji Haiku|Kireji Haiku]] 08:30, 4 October 2013 (PDT)

:::::::: BUG-4075 is a feature request for a parameter "JSON_LAST" ;) --[[User:MartinRJ Fayray|MartinRJ Fayray]] 15:32, 18 October 2013 (PDT)

== Vendor systems comparison ==

Hi.
I've tried to find the Titan vending system. It seems its no longer available. The SLURL ends in midair of a sim and you don't land at the vending center, as announced in the creators profile picks. Remove the system from the table?
--[[User:Mo Noel|Mo Noel]] 09:19, 25 November 2013 (PST)

:Did you try contacting the creator? I personally wouldn't remove the system from the table as long as it still is working and people are using it. -- [[User:Kireji Haiku|Kireji Haiku]] 03:25, 8 December 2013 (PST)

== PUBLIC_CHANNEL vs Zero ==

Seeing as this topic hasn't settled down, it's time for the larger community to choose. I view their decision (even if it's Pie) as binding.
http://www.sluniverse.com/php/vb/scripting/91061-wiki-public_channel-vs-zero.html
-- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 00:15, 1 January 2014 (PST)

All these attempts to hide the value of PUBLIC_CHANNEL need to stop. It's just spiteful Wiki editing. Any I find I'm reverting. [[User:Darien Caldwell|Darien Caldwell]] 16:11, 8 January 2014 (PST)

== JSON /de pages ==

Hello Kireji,

you somehow broke the "See also" section of two of the JSON /de pages I created (llList2Json/de, llJsonSetValue/de) in your last edits. I'm reverting them.

See: http://i.imgur.com/jLK8d0L.png

Please check the pages after changing something on them. --[[User:MartinRJ Fayray|MartinRJ Fayray]] 21:25, 11 January 2014 (PST)

LlList2Json/de

2014-01-12T05:23:21Z

MartinRJ Fayray: Undo revision 1185007 by Kireji Haiku (Talk) -- borked 'see also' section: http://i.imgur.com/jLK8d0L.png pls fix this before resubmit

{{LSL Function/de
|func_id=|func_sleep=0.0|func_energy
|func=llList2Json|return_type=string
|p1_type=string|p1_name=Typ|p1_desc=
|p2_type=list|p2_name=Werte|p2_desc=
|func_footnote=
Um einen Json-String in eine Liste zu konvertieren, verwenden Sie bitte [[llJson2List{{#var:lang}}|llJson2List]].
|func_desc=Diese Funktion erwartet eine Liste und gibt sie als [http://json.org JSON] - String zurück, entweder als JSON-Objekt oder als JSON-Array.

Gibt einen String zurück der entweder als JSON {{LSLPT|Typ}} serialisierte {{LSLPT|Werte}} enthält, oder [[JSON_INVALID{{#var:lang}}|JSON_INVALID]] wenn ein Fehler aufgetreten ist.
|spec=Siehe auch [[Json_usage_in_LSL{{#var:lang}}|Verwendung von JSON in LSL]]
* Wenn der Typ ein [[JSON_OBJECT{{#var:lang}}|JSON_OBJECT]] ist, muss die Liste eine 'strided' Liste aus Schlüssel-Wert-Paaren sein, und als Ergebnis zurückgegeben wird ein String der ein Json - Objekt darstellt.
* Wenn der Typ ein [[JSON_ARRAY{{#var:lang}}|JSON_ARRAY]] ist, wird ein String der ein Json - Array darstellt als Ergebnis zurückgegeben.
* Wenn der Typ kein String ist, wird [[JSON_INVALID{{#var:lang}}|JSON_INVALID]] zurückgegeben.
|constants={{LSL Constants/JSON{{#var:lang}}|subset=*}}
|caveats=

*LSL-Strings die mit "'''\"'''" beginnen ''und'' enden werden als JSON-Strings interpretiert. Strings ohne dieses Zeichen werden geparst wenn der String zu JSON konvertiert wird.
|examples
|helpers
|also_functions={{LSL DefineRow||[[llJson2List{{#var:lang}}|llJson2List]]|}}
{{LSL DefineRow||[[llJsonGetValue{{#var:lang}}|llJsonGetValue]]|}}
{{LSL DefineRow||[[llJsonSetValue{{#var:lang}}|llJsonSetValue]]|}}
{{LSL DefineRow||[[llJsonValueType{{#var:lang}}|llJsonValueType]]|}}
|also_constants={{LSL DefineRow||[[JSON_ARRAY{{#var:lang}}|JSON_ARRAY]]}}
{{LSL DefineRow||[[JSON_OBJECT{{#var:lang}}|JSON_OBJECT]]}}
{{LSL DefineRow||[[JSON_INVALID{{#var:lang}}|JSON_INVALID]]}}
|also_events
|also_tests
|also_articles={{LSL DefineRow||[[Typecast{{#var:lang}}|Typecast]]|}}
|notes=
|permission
|negative_index
|sort=List2Json
|cat1=List
|cat2=String
|cat3=Data Conversion
|cat4=JSON
|history = Veröffentlichungsdatum [[ Release_Notes/Second_Life_Server/13#13.05.20.276191 | 20/05/2013 ]]
|haiku={{Haiku|Their ships list to port|for what reason I know not|we list to JSON}}
{{Haiku|Listen to Jason|cryptically my sensei said|I must have misheard}}
}}

LlJsonSetValue/de

2014-01-12T05:22:12Z

MartinRJ Fayray: Undo revision 1185009 by Kireji Haiku (Talk) -- borked 'see also' section: http://i.imgur.com/jLK8d0L.png pls fix this before resubmit

{{LSL Function/de
|inject-2={{Issues/BUG-3692}}
|inject-3={{LSL_Function/negative index{{#var:lang}}|false|specifiers|nc=*}}
|func_id=|func_sleep=0.0|func_energy=10.0
|func=llJsonSetValue
|return_type=string
|p1_type=string|p1_name=Json|p1_desc=Ausgangsdaten (JSON)
|p2_type=list|p2_name=Spezifizierer|p2_desc=Position an der ein Wert hinzugefügt, geändert oder gelöscht werden soll.
|p3_type=string|p3_name=Wert|p3_desc=Der neue Wert oder [[JSON_DELETE{{#var:lang}}|JSON_DELETE]].|p3_hover=Der neue Wert oder JSON_DELETE.
|func_footnote
|func_desc=Bei Erfolg gibt diese Funktion einen neuen [http://json.org/json-de.html JSON] - ''String'' zurück, bestehend aus {{LSLPT|Json}} mit dem neuen {{LSLPT|Wert}} (an der Stelle überschrieben) der in {{LSLPT|Spezifizierer}} definiert wurde.

Wenn der Funktionsaufruf fehlschlägt (typischerweise weil ein ungültiger Array-Index außerhalb des gültigen Bereichs spezifiziert wurde) wird [[JSON_INVALID{{#var:lang}}|JSON_INVALID]] zurückgegeben.

Ein "ungültiger Array-Index außerhalb des gültigen Bereichs" (out of range array index) bedeutet, dass einer der Integer-{{LSLPT|Spezifizierer}} größer ist als die Länge des vorhandenen Arrays auf der entsprechenden Ebene mit dem Json Text, oder größer als 0 auf einer Ebene auf der kein Array existiert.

Der spezielle [[JSON_APPEND{{#var:lang}}|JSON_APPEND]] - {{LSLPT|Spezifizierer}} wird ebenfalls akzeptiert. Er fügt den {{LSLPT|Wert}} an das Ende des Arrays in der entsprechenden Ebene (definiert durch {{LSLPT|Spezifizierer}}) an. Vorsicht ist geboten, wenn diese Ebene kein Array ist, da der existierende Wert dann überschrieben wird und mit einem Array ersetzt wird, welches dann den {{LSLPT|Wert}} an der ersten Index - Stelle (0) enthält.

Im Gegensatz zu [[Liste{{#var:lang}}|Listen]] und [[String{{#var:lang}}|Strings]] werden negative Indexe in Json-Arrays '''nicht''' unterstützt.

Wenn ein existierender "Key" dem {{LSLPT|Spezifizierer}} auf der entsprechenden Ebene entspricht, wird dessen Wert mit dem neuen {{LSLPT|Wert}} überschrieben (außer wenn {{LSLPT|Wert}} der besondere [[JSON_DELETE{{#var:lang}}|JSON_DELETE]] Parameter ist).

Existiert an dieser - durch {{LSLPT|Spezifizierer}} definierten - Stelle kein Wert, wird ein neues Schlüssel-Wert-Paar innerhalb des Json-Objekts erzeugt.

Um einen existiertenden Wert an der durch {{LSLPT|Spezifizierer}} definierten Stelle zu löschen, verwenden Sie als {{LSLPT|Wert}} das Schlüsselwort [[JSON_DELETE{{#var:lang}}|JSON_DELETE]]. Dieser Vorgang entfernt dabei keine leeren Objekte oder Arrays aus höheren Ebenen.

Wenn {{LSLPT|Wert}} gleich [[JSON_TRUE{{#var:lang}}|JSON_TRUE]], [[JSON_FALSE{{#var:lang}}|JSON_FALSE]] oder [[JSON_NULL{{#var:lang}}|JSON_NULL]] ist, wird der Wert entsprechend an der durch {{LSLPT|Spezifizierer}} definierten Stelle als Text 'true', 'false' oder 'null' innerhalb von {{LSLPT|Json}} gesetzt.
|return_text=
|spec=Siehe auch [[Json_usage_in_LSL{{#var:lang}}|Verwendung von JSON in LSL]]
|constants
|caveats=

*LSL-Strings die mit "'''\"'''" beginnen ''und'' enden werden als JSON-Strings interpretiert. Strings ohne dieses Zeichen werden geparst wenn der String zu JSON konvertiert wird.
|examples=
<lsl>
string TEST_STRING_JSON;

init()
{
TEST_STRING_JSON = "[9,\"<1,1,1>\",false,{\"A\":8,\"Z\":9}]";

// [9,"<1,1,1>",false,{"A":8,"Z":9}]
say("Original TEST_STRING_JSON: " + TEST_STRING_JSON);
}

run_json_test(string input)
{
string output;

// changing values within the json string

// change the first value in the array to 10
output = llJsonSetValue(input, [0], "10");

// [10,"<1,1,1>",false,{"A":8,"Z":9}]
say("( 1): " + output);

// change the third value in the array to 'true'
output = llJsonSetValue(input, [2], JSON_TRUE);

// [9,"<1,1,1>",true,{"A":8,"Z":9}]
say("( 2): " + output);

// change the value of "A" within the Json object to 3
output = llJsonSetValue(input, [3, "A"], "3");

// [9,"<1,1,1>",false,{"A":3,"Z":9}]
say("( 3): " + output);

// adding a value or new key-value-pair within the input

// add the value "Hello" to the end of the array
// NOTE: One cannot insert, only add to the end
output = llJsonSetValue(input, [JSON_APPEND], "Hello");

// [9,"<1,1,1>",false,{"A":8,"Z":9},"Hello"]
say("( 4): " + output);

// add the key-value-pair "B":10 to the object
output = llJsonSetValue(input, [3, "B"], "10");

// [9,"<1,1,1>",false,{"A":8,"B":10,"Z":9}]
say("( 5): " + output);

// Things to look out for when modifying Json text
// ~!~ Be careful when using this function ~!~

// out of bounds array assignment:
// defined as attempting to add a value to a position ...
// ...greater than the length of the array (which may be 0)
// JSON_APPEND is ALWAYS the preferred way to add to an array
output = llJsonSetValue(input, [5], "10");

// %EF%B7%90 (URL escaped JSON_INVALID)
say("( 6): " + llEscapeURL(output));

// BUT, this works, since it is in bounds
// (eqivalent to JSON_APPEND in this case)
output = llJsonSetValue(input, [4], "10");

// [9,"<1,1,1>",false,{"A":8,"Z":9},10]
say("( 7): " + output);

// careless formation of new arrays
// ( the 4 and all subsequent 0's are all in bounds.)
output = llJsonSetValue(input, [4, 0, 0, 0], "10");

// [9,"<1,1,1>",false,{"A":8,"Z":9},[[[10]]]]
say("( 8): " + output);

// overwriting an object with an array:
// ~!~ mistaken use of JSON_APPEND on an object ~!~
output = llJsonSetValue(input, [3, JSON_APPEND], "10");

// [9,"<1,1,1>",false,[10]]
say("( 9): " + output);

// careless formation of new objects
// NOTE: "Key" assignemts will NEVER result in a return of JSON_INVALID!
output = llJsonSetValue(input, [3, "W", "X"], "10");

// [9,"<1,1,1>",false,{"A":8,"W":{"X":10},"Z":9}]
say("(10): " + output);

output = llJsonSetValue(input, [3, "W", "X", "Y"], "10");

// [9,"<1,1,1>",false,{"A":8,"W":{"X":{"Y":10}},"Z":9}]
say("(11): " + output);

// overwriting an array with an object
output = llJsonSetValue(input, ["X"], "10");

// {"X":10}
say("(12): " + output);

// special case considerations:

// BUG-3692: (NOTE: Corrected in release 13.09.21.281328!)
// a bug where, instead of JSON_INVALID being returned, if the out of
// bounds index is at a lower level than the topmost (root) level, a
// non-compliant JSON text would be formed
output = llJsonSetValue(input, [1, 7], "Disappearing Text");

// Note the "empty" second position that resulted in the returned array
// [9,,false,{"A":8,"Z":9}]
// (But now correctly shows JSON_INVALID)
say("(13): " + output);

// though there is no way to directly delete a key-value-pair
// nor remove a value from an array,
// the use of JSON_NULL may prove adequate
output = llJsonSetValue(input, [3, "A"], JSON_NULL);

// [9,"<1,1,1>",false,{"A":null,"Z":9}]
say("(14): " + output);

// if a JSON text object has been formed with llList2Json()
// that contains one or more duplicated "Keys", (allowable
// but NOT recommended!) ANY change
// made to that object will correct the condition,
// with all but the last such "Key" being removed
output = llList2Json(JSON_OBJECT, ["A", 1, "A", 2, "A", 3, "B", 4, "B", 4]);

// both Keys "A" and "B" are duplicated
// {"A":1,"A":2,"A":3,"B":4,"B":4}
say("(15): " + output);

// only the last value of the duplications is accessable though

// 3
say("(16): " + llJsonGetValue(output, ["A"]));

// condition corrected by adding a key-value-pair...

// {"A":3,"B":4,"Z":5}
say("(17): " + llJsonSetValue(output, ["Z"], "5"));

// ... or by changing a value

// {"A":5,"B":4}
say("(18): " + llJsonSetValue(output, ["A"], "5"));
}

say(string message)
{
llOwnerSay(message);
// llRegionSayTo(llGetOwner(), PUBLIC_CHANNEL, message);
// llWhisper(PUBLIC_CHANNEL, message);
}

default
{
on_rez(integer start_param)
{
llResetScript();
}

state_entry()
{
init();
}

touch_end(integer num_detected)
{
// copy 'TEST_STRING_JSON' from the following function call
// to the string 'input' in the function declaration
// and run a test on 'input' to not (!) modify 'TEST_STRING_JSON'
// but its copy instead
run_json_test(TEST_STRING_JSON);
}
}
</lsl>
|helpers
|also_functions={{LSL DefineRow||[[llList2Json{{#var:lang}}|llList2Json]]|}}
{{LSL DefineRow||[[llJson2List{{#var:lang}}|llJson2List]]|}}
{{LSL DefineRow||[[llJsonGetValue{{#var:lang}}|llJsonGetValue]]|}}
{{LSL DefineRow||[[llJsonValueType{{#var:lang}}|llJsonValueType]]|}}
|also_events
|also_tests
|also_articles={{LSL DefineRow||[[Typecast{{#var:lang}}|Typecast]]|}}
|notes=
|permission
|negative_index
|sort=JsonSetValue
|cat1=List
|cat2=String
|cat3=Data Conversion
|cat4=JSON
|history = Veröffentlichungsdatum [[ Release_Notes/Second_Life_Server/13#13.05.20.276191 | 20/05/2013 ]]
}}

User talk:Kireji Haiku

2014-01-12T05:19:28Z

MartinRJ Fayray: /* JSON /de pages */ new section

Template:JiraSearch/LSL Bugs

2014-01-10T09:56:10Z

MartinRJ Fayray: The template shall be fixed now!

<noinclude>
{{JiraSearch
|1={{Bo}}{{Bo}}urlencode:{{Bo}}{{Bo}}{{Bo}}1{{!}}{{Bc}}{{Bc}}{{Bc}}{{Bc}}{{Bc}}
|2={{Bo}}{{Bo}}{{Bo}}2{{!}}{{Bc}}{{Bc}}{{Bc}}
|description=*
|VWR=*
|SVC=*
|summary=*
|Bug=*
|Unresolved=*
|Won't Finish=*
|Scripting=*
|LSL HTTP=*
|Scripts=*
|sort/field=updated
|sort/order=desc
|sort2/field=votes
|sort2/order=desc
|ne=*
}}
</noinclude>[http://jira.secondlife.com/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery={{#if:{{{1|}}}|summary+%7E+{{urlencode:"{{{1}}}"}}+OR+description+%7E+{{urlencode:"{{{1}}}"}}}}+ORDER+BY+Created+DESC&runQuery=true {{{2|}}}]

Template:JiraSearch/LSL Bugs

2014-01-10T09:49:48Z

MartinRJ Fayray:

<noinclude>
{{JiraSearch
|1={{Bo}}{{Bo}}urlencode:{{Bo}}{{Bo}}{{Bo}}1{{!}}{{Bc}}{{Bc}}{{Bc}}{{Bc}}{{Bc}}
|2={{Bo}}{{Bo}}{{Bo}}2{{!}}{{Bc}}{{Bc}}{{Bc}}
|description=*
|VWR=*
|SVC=*
|summary=*
|Bug=*
|Unresolved=*
|Won't Finish=*
|Scripting=*
|LSL HTTP=*
|Scripts=*
|sort/field=updated
|sort/order=desc
|sort2/field=votes
|sort2/order=desc
|ne=*
}}
</noinclude>[http://jira.secondlife.com/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery={{#if:{{{1|}}}|%28summary+%7E+{{urlencode:"{{{1}}}"}}+OR+description+%7E+{{urlencode:"{{{1}}}"}}}}+ORDER+BY+Created+DESC&runQuery=true {{{2|}}}]

Template:JiraSearch/LSL Bugs

2014-01-10T09:45:01Z

MartinRJ Fayray: Fixed the right brackets this time - hopefully. Sorry for the edits, sadly I can't test this from the preview.

Template:JiraSearch/LSL Bugs

2014-01-10T09:43:49Z

MartinRJ Fayray: Missed two closing curled brackets.

<noinclude>
{{JiraSearch
|1={{Bo}}{{Bo}}urlencode:{{Bo}}{{Bo}}{{Bo}}1{{!}}{{Bc}}{{Bc}}{{Bc}}{{Bc}}{{Bc}}
|2={{Bo}}{{Bo}}{{Bo}}2{{!}}{{Bc}}{{Bc}}{{Bc}}
|description=*
|VWR=*
|SVC=*
|summary=*
|Bug=*
|Unresolved=*
|Won't Finish=*
|Scripting=*
|LSL HTTP=*
|Scripts=*
|sort/field=updated
|sort/order=desc
|sort2/field=votes
|sort2/order=desc
|ne=*
}}
</noinclude>[http://jira.secondlife.com/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery={{#if:{{{1|}}}|summary+%7E+{{urlencode:"{{{1}}}"}}}}+OR+description+%7E+{{urlencode:"{{{1}}}"}}+ORDER+BY+created&runQuery=true {{{2|}}}]

Template:JiraSearch/LSL Bugs

2014-01-10T09:40:04Z

MartinRJ Fayray: Fixing broken template. See BUG-4891

Talk:LlRotLookAt

2013-11-26T08:13:20Z

MartinRJ Fayray: Added signature./* RotLookAt, keeping one axis parallel to horizont */

An LSL example that shows how to look at some (vector) position would be nice. Every time I've looked at this call, it's been because I had an object that I wanted to look at (face) some other object or avatar. Usually, I hack at it until it works or run away and start drinking instead.

[[User:Meade Paravane|Meade Paravane]] 21:06, 18 August 2009 (UTC)

== Description is wrong and/or unhelpful ==

The description of the actual function is "Cause object to point its forward axis towards target". This makes no sense, since "target" is a rotation. What would it mean for an object to point its forward axis "towards" a rotation?

I would love to see a nice clear English description of what this function actually does. :) Every time I've started out trying to use it, I've ended up using something else (llLookAt(), or llSetRot(), or something else). Is this just the equivalent of llSetRot() for physical objects? (In which case it's odd that it works for nonphysical ones as well.) Or does it do something different / more complicated? Does the "forward" (i.e. increasing-x) axis actually play any sort of part in its function? Inquiring scripters want to know!

[[User:Dale Innis|Dale Innis]] 19:00, 21 March 2011 (PDT)

== Does anyone know... ==

...what the strength parameter actually pertains to? theoretically it could have to do with energy/mass (as some users have assumed), or it could have to do with the with the strength of the logarithmic/exponential scale of speed. I'd like to update the description, but without knowing what strength applies to (or how it's derived) it doesn't make much sense. currently my definition stands at "''smoothly changes object rotation to target over (damping)seconds''". if Strength is energy/mass related we need a formula to derive the required minimal values. If it's the logarithmic speed of change, then we need at least an estimate of the curve formula so we can derive strength values to use. -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 02:06, 4 October 2011 (PDT)

:Strength may have something to do with how hard it tries to achieve it's goal when there are competing forces. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 09:21, 5 October 2011 (PDT)
:P.S. if you figure it out, please put it in [[Template:LSL_Function/strength]] because (to my knowledge) works the same everywhere.
:P.S.S. It may be equivalent to the *_EFFICIENCY flags used in [[llSetVehicleFloatParam|vehicles]].

:Someone may want to ask Andrew about this at his office hour. {{wikipedia|Damping}} strength sounds like it might be ζ and damping is used to calculate the required velocity. ---- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 09:44, 5 October 2011 (PDT)

== Bug closed ==

The bug associated with this issue ({{Jira|SVC-1903}}) is fixed. Is there anyone maintaining that? --[[User:Pedro Oval|Pedro Oval]] 06:07, 24 January 2013 (PST)

:Thanks for the heads up. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:27, 25 January 2013 (PST)

== RotLookAt, keeping one axis parallel to horizont ==

I didn't find a code for that in the wiki, so here's a snippet of code that will make a prim look towards a position in the region, keeping one axis (x) parallel to the horizont.
<lsl>
llRotLookAtOneAxisParallelToHorizont(vector vDestPos)
{ //x-axis will stay parallel to horizont
vector pos = llGetPos();
rotation target = <0.0, -SQRT2/2.0, 0.0, SQRT2/2.0> * llRotBetween( <1.0,0.0,0.0>, <vDestPos.x, vDestPos.y, pos.z> - pos) * llRotBetween( <0.0,0.0,1.0>, vDestPos - pos);
llSetLocalRot(target);
}
default
{
state_entry()
{
}
touch_start(integer n)
{
vector detected = llDetectedPos( 0 );
llRotLookAtOneAxisParallelToHorizont(detected);
}
}
</lsl>
[[User:MartinRJ Fayray|MartinRJ Fayray]]

== Error prim exist ==

I encountered a problem caused by error prim.

llRotLookAt() or llLookAt() didn't work and llMoveToTarget() was working.

It's just a one prim sphere object.

if it turns into non physical object, llRotLookAt() or llLookAt() works and llMoveToTarget() doesn't work.

This means the object's "Physical" property works opposite feature for rotation functions.

If kind of primes are able to exist permanently, I can't trust any properties in primes.

If you want to see this error prim, please contact me, I'll give you it with a test script.

I hope it's simple mistake of mine.

Server Beta User Group

2013-11-19T20:29:13Z

MartinRJ Fayray: Added a question about latest grey-goo-protection changes on Magnum RCs.

This is the meeting tracking and progress page for the weekly Server BETA QA Meeting, moderated by Maestro Linden. Please contact him on AGNI for more information. You can join the '''Second Life Beta''' group for updates.

'''The next meeting is Thursday, November 21 2013, 3PM PST at {{SLurl|region=Morris|x=210|y=250|z=35|title=Morris}} on the preview grid, [[Preview_Grid | ADITI]].'''

* Join the email list - sign up here: https://lists.secondlife.com/cgi-bin/mailman/listinfo/server-beta

== Agenda ==

=== Updates ===
* Second Life Server
** The main channel was not rolled this week
* BlueSteel and LeTigre
** These channels got a new experience tools project
** This project just updates some of the infrastructure that experience tools use
** This project almost went to the RCs last week, but got held up at the last minute
** [[Release_Notes/Second_Life_RC_BlueSteel/13#13.11.01.283291]]
* Magnum
** Magnum got a new server maintenance project
** This project has some bug fixes and also some minor changes around script behavior
** [[Release_Notes/Second_Life_RC_Magnum/13#13.11.08.283649]]

=== Upcoming Stuff ===
* A new server maintenance project is coming soon to RC
* Group ban testing will happen in an upcoming user group. Details, about which viewer to use for the test, will follow.

=== Interesting Stuff ===
* Project Interesting viewer announced on public blog: http://community.secondlife.com/t5/Featured-News/Speedy-Delivery-Introducing-the-Project-Interesting-Viewer/ba-p/2328615

=== Any Other Items ===

== Open Items ==
* Did the changes from https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/13#13.11.08.283649 (REF: https://jira.secondlife.com/browse/BUG-4448) also affect llGiveInventory object-to-object transfers? There was some discussion about that in the Advanced Scripters of Second Life on Nov 19th, someone reported a "give inventory failure: grey goo fence: rapid or recursive inv transfer" warning on Magnum sims.

= Minutes from Previous Meetings =
*2013
** November
*** [[Beta_Server_Office_Hours/Minutes/2013-11-14 | 2013-11-14]]
*** [[Beta_Server_Office_Hours/Minutes/2013-11-07 | 2013-11-07]]
** October
*** [[Beta_Server_Office_Hours/Minutes/2013-10-31 | 2013-10-31]]
*** [[Beta_Server_Office_Hours/Minutes/2013-10-24 | 2013-10-24]]
*** [[Beta_Server_Office_Hours/Minutes/2013-10-17 | 2013-10-17]]
*** [[Beta_Server_Office_Hours/Minutes/2013-10-10 | 2013-10-10]]
*** [[Beta_Server_Office_Hours/Minutes/2013-10-03 | 2013-10-03]]
** September
*** [[Beta_Server_Office_Hours/Minutes/2013-09-26 | 2013-09-26]]
*** [[Beta_Server_Office_Hours/Minutes/2013-09-19 | 2013-09-19]]
*** [[Beta_Server_Office_Hours/Minutes/2013-09-12 | 2013-09-12]]
*** [[Beta_Server_Office_Hours/Minutes/2013-09-05 | 2013-09-05]]
** August
*** [[Beta_Server_Office_Hours/Minutes/2013-08-29 | 2013-08-29]]
*** [[Beta_Server_Office_Hours/Minutes/2013-08-22 | 2013-08-22]]
*** [[Beta_Server_Office_Hours/Minutes/2013-08-15 | 2013-08-15]]
*** [[Beta_Server_Office_Hours/Minutes/2013-08-08 | 2013-08-08]]
*** [[Beta_Server_Office_Hours/Minutes/2013-08-01 | 2013-08-01]]
** July
*** [[Beta_Server_Office_Hours/Minutes/2013-07-25 | 2013-07-25]]
*** [[Beta_Server_Office_Hours/Minutes/2013-07-18 | 2013-07-18]]
*** [[Beta_Server_Office_Hours/Minutes/2013-07-11 | 2013-07-11]]
** June
*** [[Beta_Server_Office_Hours/Minutes/2013-06-27 | 2013-06-27]]
*** [[Beta_Server_Office_Hours/Minutes/2013-06-20 | 2013-06-20]]
*** [[Beta_Server_Office_Hours/Minutes/2013-06-13 | 2013-06-13]]
*** [[Beta_Server_Office_Hours/Minutes/2013-06-06 | 2013-06-06]]
** May
*** [[Beta_Server_Office_Hours/Minutes/2013-05-30 | 2013-05-30]]
*** [[Beta_Server_Office_Hours/Minutes/2013-05-23 | 2013-05-23]]
*** [[Beta_Server_Office_Hours/Minutes/2013-05-16 | 2013-05-16]]
*** [[Beta_Server_Office_Hours/Minutes/2013-05-09 | 2013-05-09]]
*** [[Beta_Server_Office_Hours/Minutes/2013-05-02 | 2013-05-02]]
** April
*** [[Beta_Server_Office_Hours/Minutes/2013-04-25 | 2013-04-25]]
*** [[Beta_Server_Office_Hours/Minutes/2013-04-18 | 2013-04-18]]
*** [[Beta_Server_Office_Hours/Minutes/2013-04-11 | 2013-04-11]]
*** [[Beta_Server_Office_Hours/Minutes/2013-04-04 | 2013-04-04]]
** March
*** [[Beta_Server_Office_Hours/Minutes/2013-03-28 | 2013-03-28]]
*** [[Beta_Server_Office_Hours/Minutes/2013-03-21 | 2013-03-21]]
*** [[Beta_Server_Office_Hours/Minutes/2013-03-14 | 2013-03-14]]
*** [[Beta_Server_Office_Hours/Minutes/2013-03-07 | 2013-03-07]]
** February
*** [[Beta_Server_Office_Hours/Minutes/2013-02-21 | 2013-02-28]]
*** [[Beta_Server_Office_Hours/Minutes/2013-02-21 | 2013-02-21]]
*** [[Beta_Server_Office_Hours/Minutes/2013-02-07 | 2013-02-07]]
** January
*** [[Beta_Server_Office_Hours/Minutes/2013-01-31 | 2013-01-31]]
*** [[Beta_Server_Office_Hours/Minutes/2013-01-24 | 2013-01-24]]
*** [[Beta_Server_Office_Hours/Minutes/2013-01-17 | 2013-01-17]]
*** [[Beta_Server_Office_Hours/Minutes/2013-01-10 | 2013-01-10]]
*** [[Beta_Server_Office_Hours/Minutes/2013-01-03 | 2013-01-03]]
*2012
** December
*** [[Beta_Server_Office_Hours/Minutes/2012-12-13 | 2012-12-13]]
*** [[Beta_Server_Office_Hours/Minutes/2012-12-06 | 2012-12-06]]
** November
*** [[Beta_Server_Office_Hours/Minutes/2012-11-29 | 2012-11-29]]
*** [[Beta_Server_Office_Hours/Minutes/2012-11-15 | 2012-11-15]]
*** [[Beta_Server_Office_Hours/Minutes/2012-11-08 | 2012-11-08]]
** October
*** [[Beta_Server_Office_Hours/Minutes/2012-10-04 | 2012-10-04]]
** September
*** [[Beta_Server_Office_Hours/Minutes/2012-09-20 | 2012-09-20]]
*** [[Beta_Server_Office_Hours/Minutes/2012-09-13 | 2012-09-13]]
*** [[Beta_Server_Office_Hours/Minutes/2012-09-06 | 2012-09-06]]
** August
*** [[Beta_Server_Office_Hours/Minutes/2012-08-30 | 2012-08-30]]
*** [[Beta_Server_Office_Hours/Minutes/2012-08-23 | 2012-08-23]]
*** [[Beta_Server_Office_Hours/Minutes/2012-08-16 | 2012-08-16]]
*** [[Beta_Server_Office_Hours/Minutes/2012-08-09 | 2012-08-09]]
*** [[Beta_Server_Office_Hours/Minutes/2012-08-02 | 2012-08-02]]
** July
*** [[Beta_Server_Office_Hours/Minutes/2012-07-26 | 2012-07-26]]
*** [[Beta_Server_Office_Hours/Minutes/2012-07-19 | 2012-07-19]]
*** [[Beta_Server_Office_Hours/Minutes/2012-07-12 | 2012-07-12]]
*** [[Beta_Server_Office_Hours/Minutes/2012-07-05 | 2012-07-05]]
** June
*** [[Beta_Server_Office_Hours/Minutes/2012-06-28 | 2012-06-28]]
*** [[Beta_Server_Office_Hours/Minutes/2012-06-21 | 2012-06-21]]
*** [[Beta_Server_Office_Hours/Minutes/2012-06-14 | 2012-06-14]]
*** [[Beta_Server_Office_Hours/Minutes/2012-06-07 | 2012-06-07]]
** May
*** [[Beta_Server_Office_Hours/Minutes/2012-05-31 | 2012-05-31]]
*** [[Beta_Server_Office_Hours/Minutes/2012-05-24 | 2012-05-24]]
*** [[Beta_Server_Office_Hours/Minutes/2012-05-17 | 2012-05-17]]
*** [[Beta_Server_Office_Hours/Minutes/2012-05-10 | 2012-05-10]]
*** [[Beta_Server_Office_Hours/Minutes/2012-05-03 | 2012-05-03]]
** April
*** [[Beta_Server_Office_Hours/Minutes/2012-04-26 | 2012-04-26]]
*** [[Beta_Server_Office_Hours/Minutes/2012-04-19 | 2012-04-19]]
*** [[Beta_Server_Office_Hours/Minutes/2012-04-12 | 2012-04-12]]
*** [[Beta_Server_Office_Hours/Minutes/2012-04-05 | 2012-04-05]]
** March
*** [[Beta_Server_Office_Hours/Minutes/2012-03-29 | 2012-03-29]]
*** [[Beta_Server_Office_Hours/Minutes/2012-03-22 | 2012-03-22]]
*** [[Beta_Server_Office_Hours/Minutes/2012-03-15 | 2012-03-15]]
*** [[Beta_Server_Office_Hours/Minutes/2012-03-08 | 2012-03-08]]
*** [[Beta_Server_Office_Hours/Minutes/2012-03-01 | 2012-03-01]]
** February
*** [[Beta_Server_Office_Hours/Minutes/2012-02-23 | 2012-02-23]]
*** [[Beta_Server_Office_Hours/Minutes/2012-02-16 | 2012-02-16]]
*** [[Beta_Server_Office_Hours/Minutes/2012-02-09 | 2012-02-09]]
*** [[Beta_Server_Office_Hours/Minutes/2012-02-02 | 2012-02-02]]
** January
*** [[Beta_Server_Office_Hours/Minutes/2012-01-26 | 2012-01-26]]
*** [[Beta_Server_Office_Hours/Minutes/2012-01-19 | 2012-01-19]]
*** [[Beta_Server_Office_Hours/Minutes/2012-01-12 | 2012-01-12]]
*** [[Beta_Server_Office_Hours/Minutes/2012-01-05 | 2012-01-05]]
*2011
** December
*** [[Beta_Server_Office_Hours/Minutes/2011-12-15 | 2011-12-15]]
*** [[Beta_Server_Office_Hours/Minutes/2011-12-08 | 2011-12-08]]
*** [[Beta_Server_Office_Hours/Minutes/2011-12-01 | 2011-12-01]]
** November
*** 2010-11-24 *NO MEETING* Happy Thanksgiving!
*** [[Beta_Server_Office_Hours/Minutes/2011-11-17 | 2011-11-17]]
*** [[Beta_Server_Office_Hours/Minutes/2011-11-10 | 2011-11-10]]
*** [[Beta_Server_Office_Hours/Minutes/2011-11-03 | 2011-11-03]]
** October
*** [[Beta_Server_Office_Hours/Minutes/2011-10-27 | 2011-10-27]]
*** [[Beta_Server_Office_Hours/Minutes/2011-10-20 | 2011-10-20]]
*** [[Beta_Server_Office_Hours/Minutes/2011-10-13 | 2011-10-13]]
*** [[Beta_Server_Office_Hours/Minutes/2011-10-06 | 2011-10-06]]
** September
*** [[Beta_Server_Office_Hours/Minutes/2011-09-29 | 2011-09-29]]
*** [[Beta_Server_Office_Hours/Minutes/2011-09-22 | 2011-09-22]]
*** [[Beta_Server_Office_Hours/Minutes/2011-09-15 | 2011-09-15]]
*** [[Beta_Server_Office_Hours/Minutes/2011-09-08 | 2011-09-08]]
*** [[Beta_Server_Office_Hours/Minutes/2011-09-01 | 2011-09-01]]
** August
*** [[Beta_Server_Office_Hours/Minutes/2011-08-25 | 2011-08-25]]
*** 2011-08-18 *No meeting. Oskar was on vacation*
*** [[Beta_Server_Office_Hours/Minutes/2011-08-11 | 2011-08-11]]
*** [[Beta_Server_Office_Hours/Minutes/2011-08-04 | 2011-08-04]]
** July
*** [[Beta_Server_Office_Hours/Minutes/2011-07-28 | 2011-07-28]]
*** [[Beta_Server_Office_Hours/Minutes/2011-07-21 | 2011-07-21]]
*** [[Beta_Server_Office_Hours/Minutes/2011-07-14 | 2011-07-14]]
*** [[Beta_Server_Office_Hours/Minutes/2011-07-07 | 2011-07-07]]
** June
*** [[Beta_Server_Office_Hours/Minutes/2011-06-30 | 2011-06-30]]
*** [[Beta_Server_Office_Hours/Minutes/2011-06-23 | 2011-06-23]]
*** [[Beta_Server_Office_Hours/Minutes/2011-06-16 | 2011-06-16]]
*** [[Beta_Server_Office_Hours/Minutes/2011-06-09 | 2011-06-09]]
*** [[Beta_Server_Office_Hours/Minutes/2011-06-02 | 2011-06-02]]
** May
*** [[Beta_Server_Office_Hours/Minutes/2011-05-26 | 2011-05-26]]
*** [[Beta_Server_Office_Hours/Minutes/2011-05-19 | 2011-05-19]]
*** [[Beta_Server_Office_Hours/Minutes/2011-05-12 | 2011-05-12]]
*** [[Beta_Server_Office_Hours/Minutes/2011-05-05 | 2011-05-05]]
** April
*** [[Beta_Server_Office_Hours/Minutes/2011-04-28 | 2011-04-28]]
*** [[Beta_Server_Office_Hours/Minutes/2011-04-21 | 2011-04-21]]
*** [[Beta_Server_Office_Hours/Minutes/2011-04-14 | 2011-04-14]]
*** [[Beta_Server_Office_Hours/Minutes/2011-04-07 | 2011-04-07]]
** March
*** [[Beta_Server_Office_Hours/Minutes/2011-03-31 | 2011-03-31]]
*** [[Beta_Server_Office_Hours/Minutes/2011-03-24 | 2011-03-24]]
*** [[Beta_Server_Office_Hours/Minutes/2011-03-17 | 2011-03-17]]
*** [[Beta_Server_Office_Hours/Minutes/2011-03-10 | 2011-03-10]]
*** [[Beta_Server_Office_Hours/Minutes/2011-03-03 | 2011-03-03]]
** February
*** [[Beta_Server_Office_Hours/Minutes/2011-02-24 | 2011-02-24]]
*** [[Beta_Server_Office_Hours/Minutes/2011-02-17 | 2011-02-17]]
*** [[Beta_Server_Office_Hours/Minutes/2011-02-10 | 2011-02-10]]
*** [[Beta_Server_Office_Hours/Minutes/2011-02-03 | 2011-02-03]]
** January
*** [[Beta_Server_Office_Hours/Minutes/2011-01-27 | 2011-01-27]]
*** [[Beta_Server_Office_Hours/Minutes/2011-01-20 | 2011-01-20]]
*** [[Beta_Server_Office_Hours/Minutes/2011-01-13 | 2011-01-13]]
*** [[Beta_Server_Office_Hours/Minutes/2011-01-06 | 2011-01-06]]
* 2010
** December
*** 2010-12-30 *NO MEETING*
*** 2010-12-23 *NO MEETING*
*** [[Beta_Server_Office_Hours/Minutes/2010-12-16 | 2010-12-16]]
*** [[Beta_Server_Office_Hours/Minutes/2010-12-09 | 2010-12-09]]
*** [[Beta_Server_Office_Hours/Minutes/2010-12-02 | 2010-12-02]]
** November
*** 2010-11-25 *NO MEETING* Happy Thanksgiving!
*** [[Beta_Server_Office_Hours/Minutes/2010-11-18 | 2010-11-18]]
*** [[Beta_Server_Office_Hours/Minutes/2010-11-11 | 2010-11-11]]
*** [[Beta_Server_Office_Hours/Minutes/2010-11-04 | 2010-11-04]]
** October
*** [[Beta_Server_Office_Hours/Minutes/2010-10-28 | 2010-10-28]]
*** [[Beta_Server_Office_Hours/Minutes/2010-10-21 | 2010-10-21]]
*** [[Beta_Server_Office_Hours/Minutes/2010-10-14 | 2010-10-14]]
*** [[Beta_Server_Office_Hours/Minutes/2010-10-07 | 2010-10-07]]
** September
*** [[Beta_Server_Office_Hours/Minutes/2010-09-30 | 2010-09-30]]
*** [[Beta_Server_Office_Hours/Minutes/2010-09-23 | 2010-09-23]]
*** [[Beta_Server_Office_Hours/Minutes/2010-09-16 | 2010-09-16]]
*** [[Beta_Server_Office_Hours/Minutes/2010-09-09 | 2010-09-09]]
*** [[Beta_Server_Office_Hours/Minutes/2010-09-02 | 2010-09-02]]
** August
*** [[Beta_Server_Office_Hours/Minutes/2010-08-26 | 2010-08-26]]
*** [[Beta_Server_Office_Hours/Minutes/2010-08-19 | 2010-08-19]]
*** [[Beta_Server_Office_Hours/Minutes/2010-08-12 | 2010-08-12]]
*** [[Beta_Server_Office_Hours/Minutes/2010-08-05 | 2010-08-05]]
** July
*** [[Beta_Server_Office_Hours/Minutes/2010-07-29 | 2010-07-29]]
*** [[Beta_Server_Office_Hours/Minutes/2010-07-22 | 2010-07-22]]
*** [[Beta_Server_Office_Hours/Minutes/2010-07-15 | 2010-07-15]]
*** [[Beta_Server_Office_Hours/Minutes/2010-07-08 | 2010-07-08]]
*** [[Beta_Server_Office_Hours/Minutes/2010-07-01 | 2010-07-01]]
** June
*** [[Beta_Server_Office_Hours/Minutes/2010-06-24 | 2010-06-24]]
*** [[Beta_Server_Office_Hours/Minutes/2010-06-10 | 2010-06-10]]
*** [[Beta_Server_Office_Hours/Minutes/2010-06-03 | 2010-06-03]]
** May
*** [[Beta_Server_Office_Hours/Minutes/2010-05-27 | 2010-05-27]]
*** [[Beta_Server_Office_Hours/Minutes/2010-05-20 | 2010-05-20]]
*** [[Beta_Server_Office_Hours/Minutes/2010-05-13 | 2010-05-13]]
*** [[Beta_Server_Office_Hours/Minutes/2010-05-06 | 2010-05-06]]
** April
*** [[Beta_Server_Office_Hours/Minutes/2010-04-29 | 2010-04-29]]
*** [[Beta_Server_Office_Hours/Minutes/2010-04-22 | 2010-04-22]]
*** [[Beta_Server_Office_Hours/Minutes/2010-04-15 | 2010-04-15]]
*** [[Beta_Server_Office_Hours/Minutes/2010-04-08 | 2010-04-08]]
*** [[Beta_Server_Office_Hours/Minutes/2010-04-01 | 2010-04-01]]
** March
*** [[Beta_Server_Office_Hours/Minutes/2010-03-25 | 2010-03-25]]
*** [[Beta_Server_Office_Hours/Minutes/2010-03-18 | 2010-03-18]]
*** [[Beta_Server_Office_Hours/Minutes/2010-03-11 | 2010-03-11]]
*** [[Beta_Server_Office_Hours/Minutes/2010-03-04 | 2010-03-04]]
** February
*** [[Beta_Server_Office_Hours/Minutes/2010-02-25 | 2010-02-25]]
*** [[Beta_Server_Office_Hours/Minutes/2010-02-18 | 2010-02-18]]
*** [[Beta_Server_Office_Hours/Minutes/2010-02-11 | 2010-02-11]]
*** [[Beta_Server_Office_Hours/Minutes/2010-02-04 | 2010-02-04]]
** January
*** [[Beta_Server_Office_Hours/Minutes/2010-01-21 | 2010-01-21]]
*** [[Beta_Server_Office_Hours/Minutes/2010-01-14 | 2010-01-14]]
*** [[Beta_Server_Office_Hours/Minutes/2010-01-07 | 2010-01-07]]
* 2009
** December
*** [[Beta_Server_Office_Hours/Minutes/2009-12-17 | 2009-12-17]]
*** [[Beta_Server_Office_Hours/Minutes/2009-12-10 | 2009-12-10]]
*** [[Beta_Server_Office_Hours/Minutes/2009-12-04 | 2009-12-04]]
** November
*** [[Beta_Server_Office_Hours/Minutes/2009-11-26 | 2009-11-26]]
*** [[Beta_Server_Office_Hours/Minutes/2009-11-19 | 2009-11-19]]
*** [[Beta_Server_Office_Hours/Minutes/2009-11-12 | 2009-11-12]]
*** [[Beta_Server_Office_Hours/Minutes/2009-11-05 | 2009-11-05]]
** October
*** [[Beta_Server_Office_Hours/Minutes/2009-10-29 | 2009-10-29]]
*** [[Beta_Server_Office_Hours/Minutes/2009-10-22 | 2009-10-22]]
*** [[Beta_Server_Office_Hours/Minutes/2009-10-15 | 2009-10-15]]
*** [[Beta_Server_Office_Hours/Minutes/2009-10-08 | 2009-10-08]]
*** [[Beta_Server_Office_Hours/Minutes/2009-10-01 | 2009-10-01]]

[[Category:Bug Tracker]]
[[Category:Quality Assurance]]
[[Category:QA_Portal]]
[[Category:User Groups]]

Talk:Viewer 2 Microsoft Windows Builds

2013-11-11T08:52:10Z

MartinRJ Fayray: Added workaround to avoid error message when configuring with VS C++ 2010 EXPRESS version.

== A few style guidelines ==
*The person who is following these instructions for the first time may know little or nothing about VS2010. Steps should be kept simple and explained in well written English, not in a succinct description that an experienced person would be able to follow.

*If there is more than one way to do something only describe one of those ways. The philosophy at the start of this wiki page says, in part: to keep it brief, this page should only include steps we KNOW ARE NEEDED, not random hints.

*A path to, or a menu entry, should be in '''bold'''.

*A field you can change should be <code>highlighted</code>.

*Instructions should apply to Visual Studio Express. If there is a small difference between Express and Pro assume the Pro user is experienced and can figure it out. Try to avoid instructions such as "If Express do this" or "If Pro do this".

*These instructions were written collaboratively and tested by the authors for correctness in all four combinations of XP/Windows 7 and Express/Pro. If you are going to make a change to these instructions it is strongly suggested you make sure your change works for all these combinations. As your development environment may not be this extensive you may want to recruit help from people in the #opensl IRC channel who are using other OS and compiler configurations.

*Also before making a change make sure it is not an issue with your local environment. Check with others to see if they are also having this issue.

*People following these instructions still "go wrong" and come to #opensl for help. If you have the skill to contribute to improving these instructions please consider having an IRC client open to #opensl to assist people.

*The full style guideline can be found here [[Style_Guide]].

[[User:Jonathan Yap|Jonathan Yap]] 07:09, 22 June 2012 (PDT)

: I rather want to have summary, such as, the table of configuration, needed commands without step-by-step instruction. Where to go such a article? If you don't plan to have that, we'd better have two page, one is your instruction, and other is "cheat sheet". -- [[User:Mako Nozaki|Mako]] 08:54, 22 June 2012 (PDT)

::And by the wiki nature, I want every people post what they find without "filtering", accepting comments or suggestions on this wiki. If you have any comment about that, please write HERE, '''not IM to me''', to share your thought to all the people who watch this wiki. Thanks. -- [[User:Mako Nozaki|Mako]] 17:58, 22 June 2012 (PDT)

==Mailing list discussions on compile errors, and more==

=== Eliminate annoying IDE popup ===
If you are compiling with the IDE and keep getting a popup along the lines of "improve microsoft visual studio performance"
Either
*To hide on XP or 2003 Server, right-click on the Task Bar | Select Properties | Select Taskbar tab | select Hide inactive icons | Click Customize | Set the Behavior for item "Improve Microsoft Visual Studio" to "Always hide".
Or
*Follow the registry edit instructions just before "Was this information helpful?" at this link http://support.microsoft.com/kb/981741

Note: This second method did not work for me.

[[User:Jonathan Yap|Jonathan Yap]] 8:43, 31 May 2011 (PDT)

== Order of installing ==

I got errors during the installation of the directX SDK. the problems occured while it was installing the c++ Runtimes (which have already been installed before). So here is what i did to fix this:

* remove all 2010 installations
* install the DirectX SDK (June 2010) (that also installs the redistributable packages)
* Install the Visual C++ 2010 Express
* Install Windows SDK for Windows 7 and .NET Framework 4
* Run Microsoft Update

[[User:Gaia Clary|Gaia Clary]] 21:28, 8 Feb 2012 (CEST)

: FYI, This is what I find workable. If anyone stuck with the method on the article, try:

:*Install [http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-cpp-express Visual C++ 2010 Express] (Web install) or [http://go.microsoft.com/?linkid=9709969 Visual C++ 2010 Express] (ISO)
:*Install [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6B6C21D2-2006-4AFA-9702-529FA782D63B Windows SDK for Windows 7 and .NET Framework 4] (Web install) [Note: uncheck the Redistributable Package option to prevent installation failure] or [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35aeda01-421d-4ba5-b44b-543dc8c33a20 Windows SDK for Windows 7 and .NET Framework 4] (ISO)
:*Check if any Microsoft Visual C++ 2010 Redistributable Package is installed. If so, uninstall it (both x82/x64).
:*Install [http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=3021d52b-514e-41d3-ad02-438a3ba730ba DirectX SDK (June 2010)]
:*If you have default installed Direct X SDK, [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a7b7a05e-6de6-4d3a-a423-37bf0912db84&displaylang=en Microsoft Visual C++ 2010 Redistributable Package] should have been installed as well.
:*Run [http://www.update.microsoft.com/microsoftupdate/v6 Microsoft Update], and keep running it until no updates are needed. This may take 6~8 iterations on older versions of windows.
:** For Windows XP, use the provided link above. After then, use Microsoft Update on your start menu instead of default Windows Update.
:** For Windows Vista and Windows 7, you can use the link above to add Microsoft Update feature to your Windows Update. "Microsoft Update" won't on menu, so you will have to use default Windows Update to update your Visual Studios.
:** During the update cycles make sure you have picked up ”Microsoft Visual Studio 2010 Service Pack 1". If you haven't, get it from [http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=75568aa6-8107-475d-948a-ef22627e57a5 here] (Web install) or [http://go.microsoft.com/fwlink/?LinkId=210710 here] (ISO).
:-- [[User:Mako Nozaki|Mako]] 21:34, 22 June 2012 (PDT)

== Proposal: Move hints on this talk page to another page ==

Another hint. In general, we use the talk page to discuss the article itself, not for catch-all issue. See another talk pages and [[Project:Talk_Page_Guidelines]] for the references. Thus, you might want to create another page for hints, i.e. [[Viewer 2 Microsoft Windows Builds/Hint]] and move tips toward that page, and keep talk page open for people who want to say something about this article and maintenance style itself. -- [[User:Mako Nozaki|Mako]] 06:44, 22 June 2012 (PDT)
: For a starter, I withdrew my two posts about tips under my namespace, [[User:Mako Nozaki/The Solutions Against The Viewer Troubles]] since currently I can't find no suitable place to post this article in main namespace. -- [[User:Mako Nozaki|Mako]] 21:21, 22 June 2012 (PDT)

== Should always re-install Windows operation systems before you start developing viewer? ==

Related to my previous post to the first topic, this instruction seems to anticipate your Windows "cleaned". However, we may have another projects, another environment, stuffs we can't delete. If we stuck in the middle, should we every time catch someone in the IRC or delete all the environment and start from installing operation systems again? I think wiki is for sharing informations so that people don't have to repeat the similar question on the mailing list or IRC. Just thought. -- [[User:Mako Nozaki|Mako]] 17:40, 22 June 2012 (PDT)

== Visual C++ 2010 Express ==
When using the Express version of Visual C++ 2010, the "autobuild configure" step will fail due to the changes from https://jira.secondlife.com/browse/OPEN-140.
This is because the VSTool.exe application fails to return the expected value. You will receive an error message at the end of the configure step, but it is safe to ignore it.
If you are not comfortable with that error message during the configure-process, simply replace the VSTool.exe file in indra/tools/vstool/VSTool.exe with ANY .exe file that returns 0.

Talk:Viewer 2 Microsoft Windows Builds

2013-11-11T08:50:07Z

MartinRJ Fayray: I merged Jonathan Yap's and my statements about building with Visual C++ 2010 Express - I hope this is okay.

Viewer URI Name Space

2013-11-05T07:07:47Z

MartinRJ Fayray: Added caveat with ObjectIM links.

{{ProtocolNav}}

== Overview ==

The SL client supports links of the format secondlife://Region/123/45/67/, which have traditionally specified a region name and x/y/z location. This means "run Second Life viewer and show Region on the world map".

The new URL scheme has 3 slashes, and allows direct control of the user interface and login. For example, secondlife:///app/login

Most secondlife:///app URLs only work from browser instances running inside Second Life because of a denial-of-service attack using secondlife:///app/teleport links to force repeated teleports. SLURLs that work with external browsers include:
* <nowiki>secondlife://<region name></nowiki>
* secondlife:///app/login

In chat, dialogs and other user interface elements, these URLs will be highlighted as clickable links, often with custom formatting including icons. The full functionality is available in Viewer 2.0 and up. Clickable links without formatting were available only in older versions' chat and IM history.

These links also may be known as ''Viewer URL Namespace'', ''SLAPP URLs'' or ''Application SLURL''.

Enclose your links in squared brackets, or they will in some cases (e.g. for ObjectIm - links) treat all text after the link as part of the link itself (which in most cases means, the text after the link will never display). Example: [secondlife:///app/objectim/190f571d-fdf1-8f6c-4e9d-973e9b5e0566?name=ObjectName&owner=190f571d-fdf1-8f6c-4e9d-973e9b5e0566&groupowned=true&slurl=Location/128/128/27 ObjectName]

== Syntax ==

'''<nowiki>secondlife://</nowiki>'''
: '''<region_name>''' log in to this region or, if logged in, show information and offer teleport
:: '''/<local_x>''' optional X position, defaults to 128
::: '''/<local_y>''' optional Y position, defaults to 128
:::: '''/<local_z>''' optional Z position, defaults to 0

: '''/app'''
:: '''/agent'''
::: '''/<agent_id>'''
:::: '''/about''' open agent's profile, with 2nd Life tab selected
:::: '''/inspect''' display info dialog for agent (2.0)
:::: '''/im''' start an IM session with the agent (2.0)
:::: '''/offerteleport''' display teleport offer dialog (2.0)
:::: '''/pay''' display pay resident dialog (2.0)
:::: '''/requestfriend''' display friendship offer dialog (2.0)
:::: '''/mute''' add to block list (2.0)
:::: '''/unmute''' remove from block list (2.0)
:::: '''/completename''' replace the URL with the avatar's display and user names,
:::::e.g., "hmm <nowiki>secondlife:///app/agent/eea40b5a-553d-4a07-b1ca-9f6e2f867814/complete</nowiki> wow" in chat becomes "hmm Cerise (cerise.sorbet) wow" (2.4); see {{LSLGC|Avatar/Name}} for more details.
:::: '''/displayname''' replace the URL with the avatar's display name (2.4)
:::: '''/username''' replace the URL with the avatar's username e.g. "user.name" (2.4)
:: '''/appearance'''
::: '''/show''' display the sidebar appearance tab (2.0)
:: '''/balance'''
::: '''/request''' request a L$ balance update from the server (2.0)
:: '''/chat'''
::: '''/<channel>''' any channel number greater than 0 except [[DEBUG_CHANNEL]]
:::: '''/<text>'''
:: '''/classified'''
::: '''/<classified_id>'''
:::: '''/about''' open floater describing classified
:: '''/event'''
::: '''/<event_id>'''
:::: '''/about''' open floater describing event
:: '''/group'''
::: '''/<group_id>'''
:::: '''/about''' open floater describing group
:::: '''/inspect''' display info dialog for group (2.0)
::: '''/create''' open the create group dialog (1.20)
::: '''/list'''
:::: '''/show''' open the list of groups to which user belongs (1.20)
:: '''/help'''
::: '''/<help_query>''' optional help topic (2.0)
:: '''/inventory'''
::: '''/<inventory_id>'''
:::: '''/select''' inventory offer (2.0)
::: '''/show''' open the inventory sidebar tab (2.0)
:: '''/login''' log in on launch. External and internal browsers.
::: see below for query parameters, of course, values are URL escaped
:: '''/maptrackavatar'''
::: '''/<friend_id>''' find a friend on the world map, requires permission (2.4)
:: '''/objectim'''
::: '''/<object_id>''' display an info dialog for the object sending this message (2.0)
:::: '''?name=<object_name>'''
:::: '''&owner=<owner_id>'''
:::: '''&groupowned=true''' (add if the object is deeded to a group)
:::: '''&slurl=<region>/<x>/<y>/<z>'''
:: '''/parcel'''
::: '''/<parcel_id>'''
:::: '''/about''' open floater describing place
:: '''<strike>/region'''
::: '''/<region_id>'''
:::: '''/about''' information from database about that region? list of parcels? covenant?</strike>
:: '''/search'''
::: '''/<category>''' "all", "people", "places", "events", "groups", "wiki", "destinations", "classifieds"
:::: '''/<search_term>''' open a search floater with matching results (2.0)
:: '''/sharewithavatar'''
::: '''/<agent_id>''' open an inventory share/IM window for agent (2.4)
:: '''/teleport'''
::: '''/<region_name>''' teleport instantly to this region, no dialog
:::: '''/<local_x>''' optional X position, defaults to 128
::::: '''/<local_y>''' optional Y position, defaults to 128
:::::: '''/<local_z>''' optional Z position, defaults to 0
:: '''/voicecallavatar'''
::: '''/<agent_id>''' start a private voice session (2.4)
:: '''/wear_folder'''
::: '''/?folder_id=<inventory_folder_uuid>''' replace outfit with contents of specified folder (2.6)
:: '''/worldmap''' open the map with this destination selected (2.0)
::: '''/<region_name>'''
:::: '''/<local_x>''' optional X position, defaults to 128
::::: '''/<local_y>''' optional Y position, defaults to 128
:::::: '''/<local_z>''' optional Z position, defaults to 0

This could be extended to things like:
: '''/app/event/<event_id>/subscribe''' to register for notifications
: '''/app/parcel/<parcel_id>/teleport''' to teleport to a specific location

== Login Query Parameters ==
{| border="1"
|-
| first || the account first name
|-
| last || the account last name
|-
| session || the secure session id
|-
| location || login location, format TBD, optional
|}

== Examples ==

<lsl>
string Who(key id)
{
return "secondlife:///app/agent/" + (string)id + "/inspect";
}

default
{
touch_start(integer num)
{
llSay(0, "Touched by " + Who(llDetectedKey(0)) + "." );
}
}
</lsl>

[[Category:Name Spaces]]
[[Category:Search]]
[[Category:LSL Chat]]
[[Category:LSL_Dialog]]

Open Development User Group

2013-10-30T19:38:04Z

MartinRJ Fayray: add description to radar options

{{Oz/User Group Page
|purpose=
Open Source Policies, Resources for Open Contributions, and progressing contributions through the Snowstorm process.
|date-time=
Every Monday 07:00-08:00 SLT and Wednesday 15:00-16:00 SLT (see [[User:Oz_Linden/Calendar|Oz's calendar]] for exceptions) 
|location={{SLurl|region=Hippotropolis|x=209|y=90|z=24|title=Oz's Raft}}
|team=Chaired by [[User:Oz Linden|Oz Linden]] of the [[Snowstorm Team]].
|agenda=

# [http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/sunshine-external/rev/276562/index.html Sunshine-external" (276562)] build has been stuck in progress for several days. Please can someone kick it?
'''Update 08/06/2013''': Sunshine external builds are still stuck. [http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/sunshine-external/rev/276562/index.html 276562] is still in progress and so is [http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/sunshine-external/rev/276820/index.html 276820] ([[User:Whirly Fizzle|Whirly Fizzle]])

# '''Useful radar-options''' (MartinRJ Fayray --[[User:MartinRJ Fayray|MartinRJ Fayray]] 09:14, 30 October 2013 (PDT))
::Keep the current minimap (ideal for small screens), make the Radar an extra function (or have an option to minimize it so that it looks like the current minimap when it's minimized)!
::List with:
:::Name, Display Name, Distance and/or Position, Altitude, Age, Script memory and ARC/Vertices, Primcount and Scripts in viewer's region/parcel. A radar needs this basic information that helps keeping an overview of visitors and potential griefers and their position in the region.
:::with an option to mark each one on minimap, and highlighted friends and Lindens. To help distinguish individual residents on the radar.
:::indicator for "Payment-info-on-file". This helps identifying potential griefers.
:::Indicator for voice(enabled) and 'currently speaking'. To quickly identify sound sources (e.g. a resident who forgot to turn off his mic).
:::List-sort options. For better usability.
::Options:
:::context (rightclick) menu for avatar. To integrate into the current V3 interface, use the (in other places already existing) options in the contextmenu (right click on a resident or resident-name).
:::Moderation-option (block, freeze, eject, kick-ban - for parcel and estate, AR). This will help estate managers to respond quickly.
:::Request-Teleport, Offer Teleport. These options will be looked after in the radar's option intuitively by residents.
:::Show on Map. To find specific avatars in the parcel. This option already exists in the 'nearby' tab in V3, but is probably seldomly used as it is now..
:::"Look At" should be accessible if the avatar is within NearMeRange- radius (that's a debug setting used in V3 for the 'near me' floater)
::Advanced options: Get resident's UUID. Helpful for scripters who regularly need to find uuids of themselves, their customers or ALTs.
::Optional:
:::An Alert-option for new avatars and/or specific avatars could be useful, but is probably beyond scope of the project.
:::Optional Alert when avatars are entering chat range and draw distance.
::Keep the current minimap (ideal for small screens), make the Radar an extra function (or have an option to minimize it so that it looks like the current minimap when it's minimized)!


}}

Open Development User Group

2013-10-30T16:14:34Z

MartinRJ Fayray: radar

{{Oz/User Group Page
|purpose=
Open Source Policies, Resources for Open Contributions, and progressing contributions through the Snowstorm process.
|date-time=
Every Monday 07:00-08:00 SLT and Wednesday 15:00-16:00 SLT (see [[User:Oz_Linden/Calendar|Oz's calendar]] for exceptions) 
|location={{SLurl|region=Hippotropolis|x=209|y=90|z=24|title=Oz's Raft}}
|team=Chaired by [[User:Oz Linden|Oz Linden]] of the [[Snowstorm Team]].
|agenda=

# [http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/sunshine-external/rev/276562/index.html Sunshine-external" (276562)] build has been stuck in progress for several days. Please can someone kick it?
'''Update 08/06/2013''': Sunshine external builds are still stuck. [http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/sunshine-external/rev/276562/index.html 276562] is still in progress and so is [http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/sunshine-external/rev/276820/index.html 276820] ([[User:Whirly Fizzle|Whirly Fizzle]])

# '''Useful radar-options''' (MartinRJ Fayray --[[User:MartinRJ Fayray|MartinRJ Fayray]] 09:14, 30 October 2013 (PDT))
::Keep the current minimap (ideal for small screens), make the Radar an extra function (or have an option to minimize it so that it looks like the current minimap when it's minimized)!
::List with:
:::Name, Display Name, Distance and/or Position, Altitude, Age, Script memory and ARC/Vertices, Primcount and Scripts in viewer's region/parcel
:::with an option to mark each one on minimap, and highlighted friends and Lindens,
:::indicator for "Payment-info-on-file"
:::Indicator for voice(enabled) and 'currently speaking'
:::List-sort options
::Options:
:::context (rightclick) menu for avatar
:::Moderation-option (block, freeze, eject, kick-ban - for parcel and estate, AR)
:::Request-Teleport, Offer Teleport
:::Show on Map
:::"Look At" should be accessible if the avatar is within NearMeRange- radius (that's a debug setting used in V3 for the 'near me' floater)
::Advanced options: Get resident's UUID
::Optional:
:::An Alert-option for new avatars and/or specific avatars could be useful, but is probably beyond scope of the project.
:::Optional Alert when avatars are entering chat range and draw distance.
::Keep the current minimap (ideal for small screens), make the Radar an extra function (or have an option to minimize it so that it looks like the current minimap when it's minimized)!


}}

LlJsonSetValue/de

2013-10-23T06:40:39Z

MartinRJ Fayray: Added "'''\"'''" caveat.

LlList2Json/de

2013-10-23T06:38:47Z

MartinRJ Fayray: Added "'''\"'''" caveat.

JSON APPEND/de

2013-10-23T06:23:30Z

MartinRJ Fayray: Removed Multi-Lang tag.

{{LSL Constant/de
|name=JSON_APPEND
|type=integer
|value=-1
|desc=Es handelt sich um ein spezielles Spezifikationssymbol ('specifier') für die Funktion [[llJsonSetValue{{#var:lang}}|llJsonSetValue]]. Es beschreibt, dass der gegebene Wert an ein Array in einer festgelegten Ebene angehängt werden soll. Vorsicht ist geboten, wenn der Wert in dieser Ebene kein Array ist, da in diesem Fall die existierenden Daten mit den neuen Daten überschrieben werden.
|constants
|examples
|functions=
{{LSL DefineRow||[[llJsonSetValue{{#var:lang}}|llJsonSetValue]]|}}
|events
|cat1=JSON
|cat2
|cat3
|cat4
|self
}}

JSON ARRAY/de

2013-10-23T06:23:21Z

MartinRJ Fayray: Removed Multi-Lang tag.

{{LSL Constant/de
|name=JSON_ARRAY
|type=string
|value="﷒"
|dvalue={{HoverText|"﷒"|Special Unicode CharacterUnicode:	U+FDD2HTML:	&#xFDD2;llUnescapeUrl({{String|%EF%B7%92}});}}
|desc=Wird mit der [[llList2Json{{#var:lang}}|llList2Json]] - Funktion verwendet, und beschreibt dass die gegebene Liste (die auch leer sein kann) dazu verwendet werden soll, ein als String serialisiertes Json-Array zu codieren und zurückzugeben.

JSON_ARRAY ist ebenfalls ein möglicher Rückgabewert für die Funktion [[llJsonValueType{{#var:lang}}|llJsonValueType]], und beschreibt in diesem Fall dass der Json Datentyp an der durch 'Spezifizierer' definierten Stelle ein Json-Array darstellt.
|constants={{LSL Constants/JSON{{#var:lang}}}}
|examples=Erzeugen eines Json-Arrays:
<lsl>string jsonText;

default
{
state_entry()
{
jsonText = llList2Json(JSON_ARRAY, ["A", 3, "B", <1.0,1.0,1.0>, "C", "A phrase", "D", PI]);
}
touch_start(integer total_number)
{
// In the resulting Json array, all Values are separated by a comma (,).
llOwnerSay(jsonText); // ["A",3,"B","<1.000000, 1.000000, 1.000000>","C","A phrase","D",3.141593]
}
}</lsl>

Festellen ob ein Wert in einem Json Text ein Array darstellt:
<lsl>string jsonText;

default
{
state_entry()
{
// Set jsonText to [3,{"A":77,"B":66},"A phrase"]
// A Json array whose second element is a Json object
jsonText = "[3,{\"A\":77,\"B\":66},\"A phrase\"]";
llOwnerSay(jsonText);
}
touch_start(integer total_number)
{
// Test the entirety of the Json text to see if it's an array
// Note use of the empty list for this
if (llJsonValueType(jsonText, []) == JSON_ARRAY)
{
llOwnerSay("The supplied string is a Json array."); // TRUE
} else {
llOwnerSay("The supplied string is not a Json array.");
}

// Test second element of the array
if (llJsonValueType(jsonText, [1]) == JSON_ARRAY)
{
llOwnerSay("The second element of the array is a Json array.");
} else {
llOwnerSay("The second element of the array is not a Json array."); // TRUE
}
}
}</lsl>
|functions=
{{LSL DefineRow||[[llList2Json{{#var:lang}}|llList2Json]]|}}
{{LSL DefineRow||[[llJsonValueType{{#var:lang}}|llJsonValueType]]|}}
|events
|cat1=JSON
|cat2
|cat3
|cat4
|self
}}

JSON DELETE/de

2013-10-23T06:23:11Z

MartinRJ Fayray: Removed Multi-Lang tag.

{{LSL Constant/de
|name=JSON_DELETE
|type=string
|value="�"
|dvalue={{HoverText|"�"|Special Unicode CharacterUnicode:	U+FDD8HTML:	&#xFDD8;llUnescapeUrl({{String|%EF%B7%98}});}}
|desc=Eine [[:Category:LSL_Constants{{#var:lang}}|Konstante]] die dazu verwendet wird, einen Wert innerhalb eines [http://json.org/json-de.html JSON] Text-Strings zu löschen.
|constants={{LSL Constants/JSON{{#var:lang}}}}
|examples=<lsl>default
{
touch_start(integer num_detected)
{
string jsonString = "[1,2,3,4,5]";

llSay(PUBLIC_CHANNEL, "Original: " + jsonString);

// we remove the first item (list has zero-based index!)
jsonString = llJsonSetValue(jsonString, [0], JSON_DELETE);

// "[2,3,4,5]"
llSay(PUBLIC_CHANNEL, "Modified: " + jsonString);
}
}</lsl>
|caveats=*JSON_DELETE entfernt '''keine''' leeren Objekte oder Arrays aus höheren Ebenen.
|functions=
{{LSL DefineRow||[[llJsonSetValue{{#var:lang}}|llJsonSetValue]]|}}
|events
|cat1=JSON
|cat2
|cat3
|cat4
|self
}}

JSON INVALID/de

2013-10-23T06:23:00Z

MartinRJ Fayray: Removed Multi-Lang tag.

{{LSL Constant/de
|name=JSON_INVALID
|type=string
|value="﷐"
|dvalue={{HoverText|"﷐"|Special Unicode CharacterUnicode:	U+FDDOHTML:	&#xFDD0;llUnescapeUrl({{String|%EF%B7%90}});}}
|desc=Ein Rückgabewert der beschreibt, dass ein ungültiger 'Typ' in der [[llList2Json{{#var:lang}}|llList2Json]] Funktion angegeben worden ist. Ebenfalls ein Rückgabewert der [[llJsonValueType{{#var:lang}}|llJsonValueType]] Funktion, der beschreibt von welchem Datentyp die Daten in einem gegebenen, als String serialisiertem [http://json.org/json-de.html JSON]-Objekt sind.
 Außerdem ein Rückgabewert der Funktion [[llJsonGetValue{{#var:lang}}|llJsonGetValue]], um zu kennzeichnen, dass eine Spezifizierer-Angabe vergeblich versucht hat, auf Daten an einer nicht existierenden Stelle innerhalb eines Json-Texts zuzugreifen.
|constants={{LSL Constants/JSON{{#var:lang}}}}
|examples=<lsl>// Verwendung von JSON_INVALID um ein Json-Array unbekannter Länge zu durchlaufen.
string jsonText = "[1,2,3,5,6]";

default
{
touch_start(integer total_number)
{
string item;
integer iter;
while ((item = llJsonGetValue(jsonText,[iter++])) != JSON_INVALID)
{
llOwnerSay(item); // "1","2","3","5","6"
}
}
}</lsl>
|caveats=*Verwenden Sie JSON_INVALID '''nicht''' zusammen mit den Funktionen [[llList2Json{{#var:lang}}|llList2Json]] oder [[llJsonSetValue{{#var:lang}}|llJsonSetValue]]. Das Ergebnis wäre ansonsten ungültiger, nicht Json-konformer Text.

|functions=
{{LSL DefineRow||[[llList2Json{{#var:lang}}|llList2Json]]|}}
{{LSL DefineRow||[[llJsonValueType{{#var:lang}}|llJsonValueType]]|}}
|events
|cat1=JSON
|cat2
|cat3
|cat4
|self
}}

JSON NULL/de

2013-10-23T06:22:28Z

MartinRJ Fayray: Removed Multi-Lang tag.

{{LSL Constant/de
|inject-2={{Issues/BUG-3692}}
|name=JSON_NULL
|type=string
|value="�"
|dvalue={{HoverText|"�"|Special Unicode CharacterUnicode:	U+FDD5HTML:	&#xFDD5;llUnescapeUrl({{String|%EF%B7%95}});}}
|desc=Rückgabewert der Funktion [[llJsonValueType{{#var:lang}}|llJsonValueType]], die den [http://json.org/json-de.html JSON] Typ für einen Wert in Json an einer bestimmten, durch Spezifizierer definierten Stelle ermittelt.

Ebenfalls ein Rückgabewert der Funktion [[llJsonGetValue{{#var:lang}}|llJsonGetValue]], um zu kennzeichnen, dass der Text 'null' an der durch Spezifizierer definierten Stelle vorhanden war.

JSON_NULL kann auch dazu benutzt werden, um den Text 'null' innerhalb eines Json-Texts zu codieren, und so einen leeren Platzhalter ohne spezifischen Wert an der entsprechenden Stelle zu kennzeichnen (der leere LSL String "" kann stattdessen ebenfalls verwendet werden).
|constants={{LSL Constants/JSON{{#var:lang}}}}
|examples=<lsl>// Die Verwendung von JSON_NULL
// innerhalb eines Json-Text-Strings.
string jText;

default
{
state_entry(){
jText = llList2Json(JSON_OBJECT, ["A", 4, "B", 5]);
llOwnerSay(jText); // jText is '{"A":4,"B":5}'
llOwnerSay(llJsonGetValue(jText, ["B"])); // The string "5"
jText = llJsonSetValue(jText, ["B"], JSON_NULL);
llOwnerSay(jText); // jText is now '{"A":4,"B":null}'
llOwnerSay(llJsonGetValue(jText, ["B"])); // The Unicode value of JSON_NULL

}
}</lsl>
|caveats
|functions=
{{LSL DefineRow||[[llJsonValueType{{#var:lang}}|llJsonValueType]]|}}
{{LSL DefineRow||[[llJsonGetValue{{#var:lang}}|llJsonGetValue]]|}}
|events
|cat1=JSON
|cat2
|cat3
|cat4
|self
}}

LlList2Json/de

2013-10-23T06:20:22Z

MartinRJ Fayray: Removed Multi-Lang tag.

{{LSL Function/de
|func_id=|func_sleep=0.0|func_energy
|func=llList2Json|return_type=string
|p1_type=string|p1_name=Typ|p1_desc=
|p2_type=list|p2_name=Werte|p2_desc=
|func_footnote=
Um einen Json-String in eine Liste zu konvertieren, verwenden Sie bitte [[llJson2List{{#var:lang}}|llJson2List]].
|func_desc=Diese Funktion erwartet eine Liste und gibt sie als [http://json.org JSON] - String zurück, entweder als JSON-Objekt oder als JSON-Array.

Gibt einen String zurück der entweder als JSON {{LSLPT|Typ}} serialisierte {{LSLPT|Werte}} enthält, oder [[JSON_INVALID{{#var:lang}}|JSON_INVALID]] wenn ein Fehler aufgetreten ist.
|spec=Siehe auch [[Json_usage_in_LSL{{#var:lang}}|Verwendung von JSON in LSL]]
* Wenn der Typ ein [[JSON_OBJECT{{#var:lang}}|JSON_OBJECT]] ist, muss die Liste eine 'strided' Liste aus Schlüssel-Wert-Paaren sein, und als Ergebnis zurückgegeben wird ein String der ein Json - Objekt darstellt.
* Wenn der Typ ein [[JSON_ARRAY{{#var:lang}}|JSON_ARRAY]] ist, wird ein String der ein Json - Array darstellt als Ergebnis zurückgegeben.
* Wenn der Typ kein String ist, wird [[JSON_INVALID{{#var:lang}}|JSON_INVALID]] zurückgegeben.
|constants={{LSL Constants/JSON{{#var:lang}}|subset=*}}
|examples
|helpers
|also_functions={{LSL DefineRow||[[llJson2List{{#var:lang}}|llJson2List]]|}}
{{LSL DefineRow||[[llJsonGetValue{{#var:lang}}|llJsonGetValue]]|}}
{{LSL DefineRow||[[llJsonSetValue{{#var:lang}}|llJsonSetValue]]|}}
{{LSL DefineRow||[[llJsonValueType{{#var:lang}}|llJsonValueType]]|}}
|also_constants={{LSL DefineRow||[[JSON_ARRAY{{#var:lang}}|JSON_ARRAY]]}}
{{LSL DefineRow||[[JSON_OBJECT{{#var:lang}}|JSON_OBJECT]]}}
{{LSL DefineRow||[[JSON_INVALID{{#var:lang}}|JSON_INVALID]]}}
|also_events
|also_tests
|also_articles={{LSL DefineRow||[[Typecast{{#var:lang}}|Typecast]]|}}
|notes=
|permission
|negative_index
|sort=List2Json
|cat1=List
|cat2=String
|cat3=Data Conversion
|cat4=JSON
|history = Veröffentlichungsdatum [[ Release_Notes/Second_Life_Server/13#13.05.20.276191 | 20/05/2013 ]]
|haiku={{Haiku|Their ships list to port|for what reason I know not|we list to JSON}}
{{Haiku|Listen to Jason|cryptically my sensei said|I must have misheard}}
}}

User talk:Strife Onizuka

2013-10-23T06:18:55Z

MartinRJ Fayray: /* German translation of llList2Json */ added missing signature

{{:User:Zai_Lynch/Award}}You found my talk page... Find old discussions take a look at the archives: [[User:Strife_Onizuka/Talkpage_Archive_01|1]] [[User:Strife_Onizuka/Talkpage_Archive_02|2]]

== JIRA issues on LSL function pages ==

Okay, as I've made no headway deciphering your templates (not that I'm familiar in the least with the more complex wiki functions in the first place...) I decided just to cut my losses and ask! Basically I was wondering if there's a reason why [[Template:LSL_Generic/Issues]] doesn't appear to list all issues, but instead seems to just list bugs only in the same way as [[Template:LSL_Generic/Caveats]]?

I just think it'd be nice if function pages would also summarise popular proposals relating to them in the deep notes section, which is what I believed was intended but it doesn't appear to do this right now.

For example, if you go to the [[LlStartAnimation]] page, in the deep notes you'll notice that there are zero issues listed, however, clicking the "Search JIRA for related Issues" link returns quite a few. It might be nice to see the deep notes tweaked to display these, but perhaps with a limit on how many are shown (though llStartAnimation is a fairly popular one to see JIRA issues for and only has 17 issues listed). Anyway, just though I'd ask/request, please poke my talk page if you respond to be sure I remember and look! --[[User:Haravikk Mistral|Haravikk Mistral]] 15:26, 12 September 2010 (UTC)

:The template is not automatic. Take for example [[llBreakLink]], it lists a single issue in the article, it does this by including the template [[Template:Issues/SVC-3510]]. There are many stub templates like [[Template:Issues/SVC-3510]] that work this way, they contain the information about the issue and pass it along to a template that does the heavy lifting. The value of this method is that a single template exists for the Issue and if the issue is sited on multiple pages, they can all be quickly updated by modifying the template. From an organizational standpoint, it also makes it possible to see what all pertains to a particular issue.

:The thing is, if you want all the issues on the wiki, they need to be imported to the wiki, and regularly updated as changes are made... but that could all be done with a bot. Wonder if [[User:Gigs Taggart|Gigs]] could be enticed to incorporate it into [http://www.sljirastats.com SLJiraStats]?

:The goal of the Deep Notes: Issues section was to contain dead bugs and interesting feature suggestions. I never intended it to contain all issues pertaining to a feature. We don't add any value by duplicated the JIRA search engine results; the value we can add is by filtering them. Some of the bugs aren't bugs, and some of the feature suggestions are unworkable; I don't think these should be given screen space. Considering the resources required to manually include and update the issues, triage has to happen.

:Unfortunately I do not have the free time to work on this, work and other responsibilities eat all my time. *wonders just how true that is* -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 03:10, 16 September 2010 (UTC)

::Ah yeah, seems I've completely misunderstood what it was doing! I wasn't thinking to list everything, just an automatic, and hopefully useful summary of say...the top ten bugs and issues? It sounds like way more work than it's likely to be worth though so probably better just to forget about it, unless there's some way to just embed an iframe with a portion of a JIRA search or something similar? But that would probably cause an unacceptable increase in JIRA page requests from people just popping over to look something up. But now I know how it does work I can at least pop useful relevant issues on manually, thanks! -- [[User:Haravikk Mistral|Haravikk Mistral]] 12:36, 18 September 2010 (UTC)

:A related problem, I've tried to add a few top issues of interest to me onto my user page under Key Issues, however, I've tried to create two [[Template:IssueTable]] instances, but they both have the same content, despite the value of #issues being different for both. Is this some peculiarity in using this template more than once? If you could take a look at let me know it'd be handy, as IssueTable doesn't have any documentation =( -- [[User:Haravikk Mistral|Haravikk Mistral]] 11:36, 22 September 2010 (UTC)

::You are hitting one of the caveats/bugs of the new parser engine. I forget how to get around it. I beleive the issue is intermediate caching, and the way around it is to make the template call dynamic or something like that. Without spending a bunch of time debugging the problem, I just don't remember how to work around it. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 14:37, 22 September 2010 (UTC)

::It just struck me what the problem is, it's caching IssueTable. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 18:27, 22 September 2010 (UTC)

:::Aha! The "subst:" keyword seems to be for this (e.g - <code><nowiki>{{subst:User:Haravikk_Mistral/JIRA/Issues/SVC}}</nowiki></code>), as I believe it fetches the pre-processed contents of a page rather than the source. In any event, this works in my case as I created sub-pages for each category, I don't believe it would help for a page with multiple IssueTable instances though, as using subst: for any of them would just create a blank gap, but it solves my problem at least! -- [[User:Haravikk Mistral|Haravikk Mistral]] 11:29, 23 September 2010 (UTC)

== [[Ghost Detector]] ==
Thanks. I discovered that property of [[llKey2Name]] by accident. It's odd because, for instance, [[llDetectedName]] gives a non-empty string for ghosted avatars. -- [[User:Something Something|Something Something]] 05:21, 10 November 2010 (UTC)

== Friendly greetings ==
You seem to have found a "fix" for my horrible script and....messed it up. Please compare my original to yours and do some testing. They are different in the result. I would appreciate you fixing your "fix". Best regards --[[User:Kireji Haiku|Kireji Haiku]] 02:42, 14 December 2010 (UTC)

:I'm sorry you took the edit personally it was not intended that way. The example you contributed is valuable and nontrivial, however examples are held to high standards and it didn't meet them. I was faced with two options: rewriting it or deleting it, I felt it had merit so I rewrote it. My goal as always is to provide the most useful content to our users, and in this case down compatibility needed to be sacrificed. The script as it was designed required every prim to have at least one face have full glow, that didn't sound entirely useful, so I changed it to accept some glow (I notice that I also changed it to require every face have glow... which doesn't sound useful, so I'm going to revert that).
:Examples have one major goal: Be educational, teach good coding practices and problem solving. Here is where the script went awry:
:# Names should be descriptive. The function names were a bit generic but single letter variables are definitely not descriptive, especially when they are globals, they really should describe the purpose they fulfill.
:# Using globals instead of locals & parameters may be efficient, but it degrades readability and adds a new vector for script bugs. This sort of optimization has no place in examples (except in an article on optimization techniques). The situation is made even worse by using non-descriptive variable names.
:# The script contained code that complicated it without aiding readability or improving functionality. Examples need to be streamline, having it meander requires the reader to needlessly keep track of more things.
:# I felt that the functionality provided had too narrow an audience, that by changing how it functioned that it would be more useful to more people. Down compatibility is a secondary consideration for examples, not a primary consideration.

:P.S. I take it you didn't noticed there is a bug in your script: A single prim object with at least one avatar sitting on it could return the wrong result. IMO examples should not be attributed in the script text, it's what the history page is for after all, but I know the community and I don't always agree so I don't fight it. Personally I don't want my name associated with buggy code, so if you really want the script to be 100% compatible I'll have to remove my name and give you all the credit.

:P.S.S. I think we may have different notions of wiki content ownership. When I post content on the wiki, I do so with the full expectation that it will be edited, that it will mutate into something I did not envision, into something I may not entirely agree with. We do not control the content after we have posted it. It's why there is the text below the edit box: "If you don't want your writing to be edited mercilessly and redistributed at will, then don't submit it here." Wiki culture is different. I may own my contributions but I don't control their fate. They are my children, being changed and influenced by the people around them, being made stronger in the process. But I digress

:P.S.S.S. In the future if you want to convince someone they should do something, don't insult them first, it's counter productive. A better way to approach this situation would have been to say: "I disagree with some of the changes you made, specifically blah blah blah, could you please look into it? I did not appreciate your tone and I am quite insulted." It's a mistake to mix the two messages, people are prone to take offense and not do what you want out of spite. In a situation like this being snarky just isn't productive (though it does blow off a bit of steam which can feel good in the moment). Just FYI, nothing more. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 07:43, 14 December 2010 (UTC)

::I didn't take it personally and was just trying to make you aware of your rewrite not doing the same like my script. Maybe you don't read in-world messages, as I had sent you a message thanking you for your rewrite and trying to point out the differences between the two. The script I had provided would check a link-set on whether or not it has glow. And yes, that would return a false result if avatars sit on it, but I thought nobody would use the script to check if a link-set is glowing while sitting on it, but I might be wrong and should have pointed that out in the description. So I see your point there and support your critique on that. However my script would return "glowing" for a prim if ANY number of faces have SOME glow (not 1.0, as you said it would do). Maybe you now understand my view when I see your rewrite as being more streamlined and easier to read, however you limit the script down in its original ability of detecting glow by forcing it to return positive only with all faces of a prim glowing. Anyway, I'm not up for a fight and to be quite frank just too lazy for it, a builder inside of SL asked me if it's possible to detect whether or not there's a bit of glow on all prims inside a link-set of his build and I just felt like sharing my approach of writing a script for that. If that script doesn't meet wiki standards in terms of streamlining it towards being absolutely foolproof and readable for just about anybody, I'll have to refrain from doing so in future.--[[User:Kireji Haiku|Kireji Haiku]] 18:13, 14 December 2010 (UTC)

:::First I need to apologize, when I wrote my last comment I hadn't carefully reread your script, if I had I would have noticed your use of llCeil, which does as you point out return true for some glow. So my argument on that point is baseless. Between work and other obligations, I had forgotten about that aspect of the script and just went on my memory of what I thought the script was doing. As to fighting, I agree it's a waste of time and effort. However I hope you do continue to contribute to the wiki, every contribution is valuable as they grow the understanding and knowledge base of the community. Standards evolve and the content does as well, content has to be nurtured, given room to grow. Immature content just needs to mature is all; the only time stuff gets deleted is if it's factually inaccurate or needlessly repetitive. If I thought the contribution was trivial and obvious I would have stripped your name from it (attribution on one liners is blatant self ego boosting and makes the wiki look unprofessional). The only reason I attached my name was so that you wouldn't be forced to shoulder the costs of supporting code that you did not write. Please don't take away from this that your contribution was without value, or that I had no respect for it or you.

:::I should mention the reason for my terse comment in the edit was for a simple reason: I couldn't be verbose with the text limits of the field.

:::As to messaging me, all my IMs get sent to an email account I rarely check, I only ever go inworld to keep my accounts active and go to meetings (pretty rare) because my internet connect is total suckage. I had no idea you IMed me; for all correspondence I use the wiki and email.

:::You would be quite ticked at me if I were to describe my scripting habits with regards to code I post. I know I was when I saw people do what I do, but I don't really have the option. It's an ROI equation, should I make possibly buggy contributions or make no contributions at all? I wish I weren't forced to make the choice. If I weren't here doing this who would take up the mantel? Who would look after the templates? It would avoid problems like this maybe but would the community be better off? I honestly don't know but I suspect not.

:::If you're still reading, what changes or improvements would you like to see made to the documentation? An upcoming project is to incorporate collapsible sections into the documentation, I'm just not sure yet how to do so, I could do with some input. I haven't called for input from the community yet because I haven't rolled out the new Constants template yet (which will revolutionize the {{LSLGC|PrimitiveParams}} documentation). Given the potential of collapsible sections we are at a point in time where we should consider redesigning the documentation from the ground up. Maybe a contest? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:33, 14 December 2010 (UTC)

:::P.S. Does it work as it did before now? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 23:48, 14 December 2010 (UTC)

::::Hi, no it doesn't. The first problem is your thing with the double exclamation mark, that always returns 1 for me. And the second being you're still stuck with [PRIM_GLOW,ALL_SIDES], you don't do a loop through the sides. I will post a re-do of mine again, if you find a way to do what you wanted to do with the double exclamation mark thing, let me know.[[User:Kireji Haiku|Kireji Haiku]] 21:16, 17 December 2010 (UTC)

:::::<code>!![[llGetLinkNumber]]()</code> returns 1 for multiprim objects or 0 for single prim objects; It's logically equivalent to <code>llGetLinkNumber() != 0</code> however it requires less bytecode to express (you would not be without base to berate me for perpetrating this optimization/shorthand in an example script). You shouldn't need to loop through the sides, by using [[ALL_SIDES]] it should return a list containing the glow values for every side of the prim (not a very useful feature, in most cases uses it's better to loop through the sides). We then feed that list to the list stat function to get the max. I'll see if I can log in later to test it but right now I really need to fix the LSL documentation templates (the wiki upgrade broke at least one template, which in turn broke a lot of the LSL documentation; I'm trying to both find and fix the broken templates; and I don't know the precise cause). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:37, 17 December 2010 (UTC)

::::::Fixed it finally, thanks again for the ideas and the input. <code>!![[llGetLinkNumber]]()</code> doesn't seem to work, I know exactly what you're trying to do by writing it that way, but that always returns 1. Have tested it. And your return was a bit too fast to return a result, wouldn't wait until the end. If you can simplify it even further, go ahead. That's as far as I could get.[[User:Kireji Haiku|Kireji Haiku]] 21:12, 23 December 2010 (UTC)

:::::::Is <code>!![[llGetLinkNumber]]</code> returning one for a single prim object with no avatars sitting on it? That is the only time it should return zero. A single prim object with a seated avatar should return one. As to the early exit, once we find a prim with no glow, we can exit without checking the other prims. Logically speaking, we do not need to know precisely what the minimum is, just if it is less than or equal to zero. So instead of calculating the minimum we can exit as soon as we know the minimum is going to be less than or equal to zero. We know it will be less than or equal to zero if we have a value that is zero or less. The code should exit as soon as it knows the answer so as to not waste simulator resources (after all we need to encourage responsible coding). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 05:08, 25 December 2010 (UTC)
::::::::Personally, I would prefer that examples intended to educate and demonstrate functionality NOT have obfuscating optimizations in them, unless the purpose of the example is to demonstrate such. It makes it harder for non-gurus to understand what is going on in the script, thus limiting the "educational value" of the example and obviating the purpose which it was intended. That said, I do believe it is important for people to know about them as well as how/when to use them, but I also believe teaching good programming habits is also valuable. (I don't know if the script in question qualifies as such; just wanted to point this out since it came up as an ancillary issue) [[User:Talarus Luan|Talarus Luan]] 07:35, 15 January 2011 (UTC)

== Help with template issue ==

Hi Strife,
I'm hoping you can help to shed some light on a problem we have just discovered that has started to occur since we redployed the wiki yesterday. The symptom is that SOME pages, e.g. [[LlKey2Name]] display differently when you are not logged in versus logged in. Compare
* Logged in: http://screencast.com/t/e3K85IGni
* Not logged in: http://screencast.com/t/4OwWfihvhi
I ''think'' that this may be happening due to issues around templates, which is why I am contacting you. However, I don't really know the cause. The strange thing is that most other LSL function pages appear to display just fine when you are logged out; so there must be something in that page causing an issue. We would greatly appreciate any help! P.S. Here is the whole list of known issues: [[Second Life Wiki Known Issues]].

Thanks
--[[User:Rand Linden|Rand Linden]] 17:15, 16 December 2010 (UTC)

:I think it was generated before the extensions were installed. I purged the page (?action=purge) and it now renders properly for me (though I did see it the way you described but only when i was not logged in). It's weird. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:22, 16 December 2010 (UTC)

::Maybe the cache just needs to be invalidated? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:24, 16 December 2010 (UTC)

::Some triangulation: <nowiki>|constants={{LSL Constants/PrimitiveParams|get}}</nowiki> does ''not'' cause trouble on a test copy of llSetLinkPrimitiveParams, <nowiki>|constants={{LSL Constants/PrimitiveParams|set}}</nowiki> triggers the bug. Off to try on simpler stuff to see if there is a consistent pattern of some kind ... --[[User:Cerise Sorbet|Cerise Sorbet]] 21:47, 16 December 2010 (UTC)

::The cache is not invalidating or refreshing. Check the mod date at the bottom of [[http://wiki.secondlife.com/wiki/LlSetLinkPrimitiveParamsFast]] and [[https://wiki.secondlife.com/wiki/LlSetLinkPrimitiveParamsFast]]. They are different. If you go into the history page and look at a previous version it will displays properly because it doesn't have a cached version but if you look at the current version (even with the version number, it does not display properly). Not even action=purge can budge it. A possible explanation is that the PrimitiveParams article is causing it to time out during rebuild. The new version of the template I'm hoping to get done by new year should be more sane and less time consuming (we hope). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:00, 16 December 2010 (UTC)

:: I thought it was only cache too but more appears to be going on. [[llKey2Name]] is displaying OK with a pair of Issue templates commented out. --[[User:Cerise Sorbet|Cerise Sorbet]] 22:22, 16 December 2010 (UTC)

:::The time issue I was seeing was caused by me having my account report the times in GMT+5 (which is weird seeing as i'm GMT-5) -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:31, 16 December 2010 (UTC)

:I've had a thought, I think it might have something to do with how bugs are duplicated (in both Issues and Important Issues). It looks to be the difference between the Get and Set primitive Params functions (Get are too new to have any flag bugs). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:42, 16 December 2010 (UTC)

::It's not [[Template:Issues]] that is doing it, it's something about [[Template:Issue]]. I have this terrible feeling it's a problem with how #switch is parsed. When are we getting the new parser function extension? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:55, 16 December 2010 (UTC)

:::Oh it's definitely [[Template:Issue]]. I can't access it when logged out. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:55, 16 December 2010 (UTC)

::::I've disabled the code that detects if an issue is a bug, which appears to have fixed [[llKey2Name]]. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 23:14, 16 December 2010 (UTC)

: #switch is not the cause, just the trigger. Maybe it's content duplication that is the problem? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:28, 17 December 2010 (UTC)

: Mediawiki 1.14 added a |link= option for Image: tags. This would let you skip the imagemap for most uses that don't really need coordinates. --[[User:Cerise Resident|Cerise]] 03:38, 18 December 2010 (UTC)

:: There is a god ^_^ thanks for the tip. I'll deploy it post hast. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 03:40, 18 December 2010 (UTC)

::: Thanks so much for tracking this down, Strife and Cerise! This move/upgrade has certainly been more problematic than we expected.... :-(
:::--[[User:Rand Linden|Rand Linden]] 19:05, 19 December 2010 (UTC)

:::: They always are more problematic than anticipated. I'm sorry I didn't pay more attention to it earlier, I did notice the blanking on the test wiki briefly but not the common factor (since I spend all my time logged in, the first thing I always do when I connect is log in). I spent my time looking at differences between the highlighting. Never thought to look for differences between HTTP & HTTPS. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 19:30, 19 December 2010 (UTC)

== Different versions of UTF-8 libraries ==

Hi Strife, it seems that there are two different versions of both UTF8ToUnicodeInteger() and UnicodeIntegerToUTF8() at [[Combined_Library#Unicode_functions]] and [[UTF-8]]. Maybe those could be moved to a template - or just manually synced as you feel appropriate. --[[User:Opensource Obscure|oobscure]] 03:17, 2 May 2011 (PDT)

There is a good point. Will do. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 09:12, 12 May 2011 (PDT)

== Issues/SCR-137 ==

Sorry for [[Template:Issues/SCR-137]], force of habit since most of the time I'm suggesting new functions that aren't on the wiki, rather than changes to existing ones ;) -- -- '''[[User:Haravikk_Mistral|Haravikk]]''' ([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]]) 01:43, 9 July 2011 (PDT)

:No need to apologize. In my diminished capacity these days (being cut off from SL due to network restrictions for such a long time) there is little I can do besides act as editor, and theoretical scripting. So you gave me something to do. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 09:10, 9 July 2011 (PDT)

== llCastRay Docs ==

Thanks, Strife. Your improvement to the llCastRay docs look great.

[[User:Falcon Linden|Falcon Linden]] 11:57, 1 September 2011 (PDT)

== User Functions ==

Heya Strife,
Could you give me a headsup how the wiki format for Mode=User LSL Functions are meant to be used like?

https://wiki.secondlife.com/wiki/Interpolation/Linear/Float

I'm not sure why I can't get rid off the "Deep Notes" section, which seems sorta empty and useless?

[[User:Nexii Malthus|Nexii Malthus]] 11:48, 17 September 2011 (PDT)

:Sure -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:36, 18 September 2011 (PDT)

== Video Documentations / Tutorials ==
forgot who the king of confirming stuff on this wiki is, I haven't been an editor for like a year or two if you remember me or not, but I thought I might add video documentations and tutorials on functions that could be confusing on the wikis page, so I guess the question is how should I add the videos, should I add a new category or just put it in the examples category, and if video documentation is a good idea toward you, since you are the #1 editor on this wiki haha, and I know nothing about style D:
----[[File:Uglehsig.png|53px|link=User:Ugleh_Ulrik]]([[User_talk:Ugleh_Ulrik|talk]]) 19:45, 11 October 2011 (PDT)

:I'm tickled that you would consult me but I really have no idea on this one. I think it's a great idea and until we get more of them to get a feel as to how they can be best incorporated into the documentation, they can be included any way you see fit. I might suggested posting the question to the script forums and mailing list (if you do, maybe post a link so I can follow along?). I can imagine putting them in See Also, Examples, Deep Notes, Helpers, Specification (maybe?), Newbie Notes, Notes. I have trouble seeing them in the Summary/Description, Caveats or Constants. Maybe float them on the right (like in [[PRIM_MATERIAL]])? Keep up the good work. ^_^ -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 12:21, 12 October 2011 (PDT)

== Hi ==

Just caught the comment over on the blog and wanted to say hi. I haven't left, just withdrawn from the official forums. Actually I hopped over to SLU, although their scripting forums are dead as doornails, so I've been amusing myself in their PRS section. Sent in an NDA for the latest inworld beta review project, no reply yet ::shrug:: hope all is good on your end, and was pleasantly surprised you stopped by. Cheers -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 07:52, 22 December 2011 (PST)

: Things are going well here. beta? do they have a page describing it anywhere? I always loved betas. I stay mostly here on the wiki, wish I could get in world more, I hate writing documentation without being able to test the functionality. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 23:22, 22 December 2011 (PST)
:P.S. You are a braver soul than I to go into PRS.

No wiki page that I'm aware of, e-mail invitation letters (which seem to have been dispersed to many forumites, and turned down by a few) describe it as pre-release feedback review, of what specifically, I couldn't say (even if I knew yet). I'll ask if they'll bounce you a late entry since you seem interested. and yeah PRS is madness, but I'm largely word-proof so the invective is more like warm glow instead of singing flame for me, something to kill break time. happy new years and all that jazz -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 10:00, 26 December 2011 (PST)

:Thank you for offering but It's better if you don't. I wish I could thou I have no time (nor the internet connection) for it. If they sent me an invitation I'd feel obliged to accept and then not be able to do it justice. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:55, 26 December 2011 (PST)

Understood, I'll try to remember to ping ya when it goes live then, could be a bit, dunno quite how far they are out on it. -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 16:22, 27 December 2011 (PST)

== http_response event only be triggered for the originating script or triggered for all scripts ==

Hello Strife,

I just read the [http://wiki.secondlife.com/w/index.php?title=LlHTTPRequest&diff=1157547&oldid=1157508 note] you added concerning [[llHTTPRequest]].
Although this is of course a sane behavior, I was a bit surprised when I read it because I knew it wasn't the case before, I also have some script that depends on the old behavior and I didn't received any complaints concerning them.
So, I've just checked and I can confirm that, at least on my home sim which use the main server version, the event is still triggered on all scripts of the object which made the request.

By pure curiosity, I wonder if you have any additional information about this change.

Many thanks,
[[User:Elena Bouscario|Elena]] 11:45, 11 February 2012 (PST)

:I have no information on this unfortunately. My edit was a rewrite of the [https://wiki.secondlife.com/w/index.php?title=LlHTTPRequest&diff=1157508&oldid=1153608 previous edit] so that everything would read more clearly. Sounds like both edits should be reverted. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:45, 12 February 2012 (PST)

== capturing caveats in constants pages? ==

I'm trying to figure out the proper way to include a caveat in the [[DEBUG_CHANNEL]] and [[PUBLIC_CHANNEL]] pages, so that it properly inserts into articles referencing those two pages. The caveat is as follows
* Messages on channel_name are throttled to a rate of <200/2sec, per region, per owner/user.
** Once the rate is exceeded, all messages on channel_name will be dropped until the send rate is again below 200/2sec for the previous 2 sec.
not quite sure how to go about it though? -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 23:27, 21 August 2012 (PDT)

:I'd be inclined to work it into [[Template:LSL_Function/chat]] as well. No time now (and likely won't be able to see later, going to the eye doctor). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 08:30, 22 August 2012 (PDT)

:Arrg it's a rats nest. I'll work on it later. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 08:31, 22 August 2012 (PDT)

:I've put it in the template so now it's now everywhere... but still needs some tweaking. back later -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])

Thanks, didn't mean to give you headaches over it =( I'll take a look at how you did it so maybe next time I can sort it myself -- '''[[User:Void_Singer|Void]]''' ([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]]) 21:47, 22 August 2012 (PDT)

:It wasn't as bad as I thought it would be, no worries. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 08:48, 23 August 2012 (PDT)

== llGetTime/llResetTime ==
I saw you made a distinction between Mono and LSO for whether or not it's affected by dilation. However, empirical evidence doesn't seem to support this. While this may have been true in the past, it doesn't seem to be anymore. [[User:Darien Caldwell|Darien Caldwell]] 11:08, 13 September 2012 (PDT)

:That is great. :) I'll revert it. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:20, 13 September 2012 (PDT)

== Another world, another wiki ==

I don't suppose you have any tips for a budding documentor? I'm just learning mediawiki, and started function documentation over at Cloud Party (I didn't create the templates) http://wiki.cloudpartytime.com
BTW, do you use avisynth, or work on wiki docs for it? Still enjoy tinkering with avisyth scripts! [[User:Phate Shepherd|Phate Shepherd]] 16:43, 16 September 2012 (PDT)

:I'm sorry it's been taking me so long to respond, I'm working on articulating the my thoughts. I haven't forgotten you. I want to do the questions justice. Watch this space for an update soon. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:29, 19 September 2012 (PDT)

::No worries... So much to do and learn here! Thanks![[User:Phate Shepherd|Phate Shepherd]] 22:06, 21 September 2012 (PDT)

:I had a partial response all ready written and then my computer crashed. Here is a reconstruction:
:# Find some documentation you really like, and copy it's good features. Find some bad documentation and figure out what you don't like.
:# Write a mission statement for you wiki based documentation project. It should be short and concise. Then write a longer description after it as to what it means. As a matter of course your project will attract people sooner or later who won't share your vision. Having something in writing you can beat them over the head with will help reduce the toll the drama will have upon you. I'd give you more advise along these lines but it might be too specific and never crop up (it's the subtle difference between keeping a loaded gun and keeping a loaded cross bow that shoots wooden stakes). Be sure to have a well spelled out contribution policy, specifically content must be licensed under a wiki specified license but that doesn't mean the author cannot dual license it under another license if they so choose (they just can't choose to not license it under the wiki license).
:# Don't feel you need to do everything. You are a volunteer. You volunteer. You do it for free. You aren't obligated to do anything. It's not like they are paying you. So when you feel stressed, that it is going to hell, remember this, take a deep breath and relax, if they want to avert catastrophe they can spend money. If the catastrophe can't be averted with money then there is nothing you could do about it, so there is no reason for you to be stressed about it. It's not your problem.
:#* I have many wiki projects, in various states of completion. Some have been in the works for years, that is to say, I haven't really done anything with them for a considerable amount of time.
:# If you want something done, you will probably have to do it yourself. You won't be able to convince anyone else to do it. {{LSLGC|Needs_Example}} grows, it doesn't shrink.
:# Engage your community. Ask them what they want out of the documentation. Ask them how to make it better. This will encourage them to help you. Be prepared to hold their hands and show them how to edit the documentation. This is how you cultivate contributors. This is how you cultivate a contributor community.
:# The quality of documentation is determined by the audience. You should choose an audience to server and put that in your mission or goal statement. Serving a diverse audience is going to require negotiating some very complex tradeoffs.
:#* The LSL documentation have [[LSL_Portal_Guidelines|mission and goal statements]] that are at odds with each other. The type of help a beginner needs is not the same as that of an expert. A beginner needs it simple, an expert needs it precise. The solution is a layout that tries to divide the problem into manageable chunks. However getting that solution realized has been difficult.
:# If you have an issue tracker, add links in your documentation to pertinent issue in the tracker. Update them on a regular basis. If you can make it auto-update.
:P.S. Those templates are cool. I've been trying to mimic some of those features for years (not impossible but I run the risk of killing the wiki).
:-- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:10, 27 September 2012 (PDT)
::Thanks for taking to the time to write that out... I'll try and take it to heart. As for the "Find a wiki you like...." Well, that's why I came to you ;-) [[User:Phate Shepherd|Phate Shepherd]] 12:58, 28 September 2012 (PDT)

== [[Hierarchics]] Reboot ==
Yeah, well, I had tested a modern slaveless version several times over. But each time I still hit significant performance issues.
I had instead started using newer techniques for achieving realtime high performance animated skeletons, see:
http://youtu.be/mZvV-1Ghxt0
http://youtu.be/KwFdahxZp7M
Unfortunately it is hard to document the scripting process, as it means using global variables for each part in the skeleton and using batched input-process-render stages. --[[User:Nexii Malthus|Nexii Malthus]] 08:05, 7 October 2012 (PDT)

== LSL Tip ==
Hiya, so what about the [[Template:LSL Tip]] template? Are you gonna keep the warning text? We could use the [[Template:KBcaution]] or [[Template:KBtip]] templates instead. -- [[User:Kireji Haiku|Kireji Haiku]] 03:27, 18 October 2012 (PDT)

:I like both of those. Lets go with [[Template:KBcaution]] for now. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:14, 18 October 2012 (PDT)

:P.S. Added bonus: those templates were internationalized already.

== Any idea why embedded video (youtube or vimeo) is not showing? ==

Hiya Strife. Hope this finds you well :-)

On [[User:Fred_Gandt/Tuition|Fred_Gandt/Tuition]] and even [[Torley]]'s pages, embedded videos are not showing up for me. Is it just me (using Chrome on Win7)?  [[User:Fred_Gandt|'''fredgandt''']] 00:54, 2 November 2012 (PDT)

:Seems to be working for me. Even the one on my user page. It's probably something to do with chrome. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 01:58, 2 November 2012 (PDT)

::Meh. I'll try clearing some cookies and stuff. Thanks for checking and confirming it's at my end.  [[User:Fred_Gandt|'''fredgandt''']] 02:31, 2 November 2012 (PDT)
::Chrome is flagging all youtube vids embedded using <nowiki><videoflash></nowiki> tags as "insecure". Can someone get at the parser and set it to use https instead of http?  [[User:Fred_Gandt|'''fredgandt''']]

::I was about to ask Torley to take a look at the issue, but found he is off doing something else. I'm assuming you can act as an admin around here. Shit! You pretty much run the place :-)
::So when viewing the wiki under https, all videoflash is regarded as insecure. The issue is in [http://www.mediawiki.org/wiki/Extension:VideoFlash the mediawiki extension]. All the protocols are hard wired to http, so on a secure page, they are poop. I'd suggest (if possible) relative protocols or at least selective rewriting to allow https where available. YouTube is definitely available secure, and I think vimeo is too. Obviously hard wiring them (so to speak) as https would mean that https wiki pages would be happy and http wikipages wouldn't care one way or the other.
::Why does it matter? Videos are missing if a viewer's browser blocks the content. I took the time to find it, whilst others might not. Also: insecure content on a secure site is just poor practice. [[User:Fred_Gandt|'''fredgandt''']] 10:32, 4 November 2012 (PST)

== Request from inworld teacher ==

Would it be possible to encourage new users to append "better" versions at the bottom on users pages? Recently many of the pages I use for teaching classes have been "improved" which results in material which doesn't match our class notes, and in one case totally wiped out homework we give to see if students understand the concepts just taught! I am not talking about the LSL-101 pages which are in the shared userspace of the wiki. I am talking about my own user pages. I can see that we have a new enthusiast who wishes to fix everything all at once, but can I beg for discussion instead of reversions to user pages? Different people use their pages for different reasons. I am sure that many if not all of these script changes are excellent, but without an explanation to student users it's like changing a telegraph to a cellphone. It's "better," but incomprehensible.

In reviewing all my pages, I found a part where you changed things like ''for (i = 0; i < c; i = i + 1)'' to ''for (; i < c; ++i)'' which is fabulous, but without an explanation that the two are the same, most of the free scripts in SL just became incomprehensible to someone trying to teach themselves without a formal scripting background. My classes are aimed at the non-scriptor. Please when you make higher level changes on my user pages, please leave both versions and maybe explain why they are same/different? We have avid learners, but most of this wiki is like trying to read ancient Greek with a Russian translator.

I always thought in a wiki that "user" pages were allowed to the users to edit, with the "talk" or "discussion" pages being where to argue out the fine points. Maybe I'm wrong, but I would appreciate it if people would do what you do, make small changes at each edit, else append changes instead of wiping out whole scripts which match inworld classnotes, some of which date back to Eric Linden. [[User:Toady Nakamura|Toady Nakamura]] 09:39, 4 November 2012 (PST)

:I and [[User:Daemonika Nightfire|Daemonika Nightfire]] had our user pages defiled too. I recommend reverting and asking Kireji to back the F**k off. But then I'm not very political.  [[User:Fred_Gandt|'''fredgandt''']] 09:51, 4 November 2012 (PST)

::I'm thinking a conversation about the semi-sanctity of userpages is in order. It's gone further then I would have gone with it. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:10, 4 November 2012 (PST)

:I try to not mess with code unless I'm fixing a (logical) bug in the code or a gross inefficiency. Programming style is something I view as a personal preference and I would only mess with if I were fixing something major. People are attached to their user pages and take particular interest in controlling them so I try to turn a blind eye to them.

:As to the public tutorials, they are public and subject to change. Positive change is a good thing, negative change is not. The only thing I can offer is to use the permanent link button so you always get the same revision. As you say without an explanation somewhere that ''for (i = 0; i < c; i = i + 1)'' to ''for (; i < c; ++i)'' are often the same, how are people to know. This is precisely the sort of thing that needs to go in the tutorials. Or at least in the article on [[for]].

:I do recognize that most of the language of the wiki is technical. There are places (entire sections) for less technical language but they aren't documented and the project lacks a champion. History has demonstrated that while I am open to the concept of having it in the documentation, I cannot write that aspect of the documentation. Find me someone who is driven to write readable documentation and I'll bend over backwards to find space for it in the documentation (You might want to look at [[llSetColor]]) -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:10, 4 November 2012 (PST).

:P.S. Maybe we need a list of pages that are too opaque and in need of improvement.
:P.S.S. Remember this is a wiki, if we agree, we can change everything. Nothing is sacred. The only limits are our imagination (and what the wiki can handle before it implodes). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:13, 4 November 2012 (PST)

::I am inclined to defer to Wikipedia etiquette for no lesser reason than Wikipedia is the daddy of wiki's and gets it done (however anal it may be). See [http://en.wikipedia.org/wiki/Wikipedia:User_pages#Ownership_and_editing_of_user_pages guidelines on ownership] and (same page)[http://en.wikipedia.org/wiki/Wikipedia:User_pages#Editing_of_other_editors.27_user_and_user_talk_pages common practices specific to editing userspace pages]. Clearly if "the project" is the SL wiki, userspace pages would therefore feature in much the same way as they do on Wikipedia. Where tuition (especially) is concerned, scripts and examples are difficult to regard in the normal sense. Scripts written to show poor or extremely simplified methods may be valid. Large amounts of comments would also be perfectly acceptable.
::More importantly; scripts on user pages here are copied and used by people inworld, and how well (or badly) they perform reflects on the writer. I (for example) state that I do my best to make sure the scripts function correctly (although I don't get inworld much anymore and there may have been significant changes that cause some of my scripts to go wronger than they used to). I can't claim to have made every effort to ensure the workingnessability of a script if someone has come along and changed it!!
::Moreover; It's a matter of common courtesy. Sure we don't own the pages, but seriously?!?
::If you visit a public building and another visitor comes along and pulls the rug out from under you, is that acceptable? It doesn't really matter who owns the pages. It's what they are that matters. They are predominantly used as a repository for user created content that is being given away or as examples. As [[User:Daemonika Nightfire|Daemonika Nightfire]] said when discussing [[User:Kireji Haiku|Kireji Haiku]]'s edits, she doesn't want to have to learn how her scripts work if someone asks her about them.
::I get emails now and then from people who want me to change features of some of my scripts for custom projects. If I came to grab a copy and found it wasn't what I wrote, but the other user though it was, I would have to either learn the new version or explain that someone else wrote it.
::If someone else wrote it, why the f**k is it on my user page with a heading exclaiming that I did?!
::<s>If it's decided that user pages (other than talk pages) can be freely edited by all and sundry, then I will ask that all my pages be deleted. Sounds precious? Try again.</s> [[User:Fred_Gandt|'''fredgandt''']] 10:58, 4 November 2012 (PST)

My two cents are on the topic are on [[User talk:Kireji Haiku|my user page]]. -- [[User:Kireji Haiku|Kireji Haiku]] 12:10, 5 November 2012 (PST)

== Table within table?! ==

Hi, I wanted to put a side-by-side comparison table:

{| class="sortable" width="100%" {{Prettytable}}
|- {{Hl2}}
! '''Method one: returns float within (5.0, 10.0]'''
! '''Method two: returns float within (5.0, 10.0]'''
|-
||<lsl>
default
{
state_entry()
{
float randomFloat = 10.0 + llFrand(-5.0);

llSay(PUBLIC_CHANNEL, randomFloat);
}
}
</lsl>
||
<lsl>
default
{
state_entry()
{
float randomFloat = 10.0 - llFrand(5.0);

llSay(PUBLIC_CHANNEL, randomFloat);
}
}
</lsl>
|}

into the example section on the [[llFrand]] page. As far as I understand, that would be a table within a table, yes? Is it possible, if so how? -- [[User:Kireji Haiku|Kireji Haiku]] 10:19, 9 November 2012 (PST)
:Ok, I can rip the html code off the template. Any other way with the wiki markup? -- [[User:Kireji Haiku|Kireji Haiku]] 11:52, 9 November 2012 (PST)

::To do tables within tables I think you need to escape the pipes. Or that is how we use to do it when it was called for (they may have fixed that bug in mediawiki ages ago). Use <nowiki>{{!}}</nowiki> it's a specalized template for this exact purpose. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:27, 19 November 2012 (PST)

== Entry level information on LSL wiki pages ==

Hello again. I spent time over the last month looking at the "newbie Notes" as the example you provided on llSetColor. While I have the skill set to edit for this wiki at that level, I have found myself hesitating to start anymore "newbie Notes" because:

*"Newbie" is not necessarily a nice word. I feel that people seeking entry level material should not be categorized with a pejorative.

*The extra set of pages eg: llSetColor Main Page and llSetColor Basic Notes would create a parallel and confusing architecture.

I would like to suggest that instead of erecting a duplicate set of pages for all of the nearly 300 Linden Library functions and some dozens of events, that a section at the bottom of each function page be started for "entry level notes." After scrolling through the first page or two, any new user would rapidly find the "expert section" and the "entry level section" tucked at the bottom of the main page.

If that would be agreeable to you, I would be happy to undertake entry level editing of functions and events pages as time permits. [[User:Toady Nakamura|Toady Nakamura]] 09:48, 7 December 2012 (PST)

:I'm not exactly sure what notes are "newbie notes" (can't recall ever seeing any) but I partially agree with your apprehension about the pejorative.
:I personally don't find the word anything but honest, although I can imagine some feeling it derogatory or exclusive.
:Regarding "Entry level" notes: I feel that every page should start out (top to bottom) with entry level information, leading through examples to higher level notes.
:I don't think a generic technical description should be then followed by notes for people who (by implication) didn't understand it, then notes for people who understood it but need more.
:I'd be all in favour of pages being custom built to suit the subject, utilizing an info-box for the technical break-down, whilst the rest of the page is lane out in a less uniformed, and more uniquely useful style.
:Consider the difference between e.g. [[llSay]] and [[llHTTPResponse]]. Anyone reading the wiki to learn about llSay, will almost certainly need the subject explained in simple non-technical terms, than someone reading the entry for llHTTPResponse. Both should contain all the same (relative) information, but the style and flow of how that information is presented should reflect the individual case at hand.
:The difficulty in deciding to make special notes for special people is, who decides who is special?
:An expert programmer in another language would need a completely different set of "newbie notes" to someone who knew jack shit about programming. The former would need the technical details about this weird language explained (such as arbitrary delays), whereas the later wouldn't know why that needs explaining (they'd more likely just accept it). They would however need to know what comma separating function arguments is all about.
:What would probably work best, is something that is unlikely to be done. If every page was rewritten two more times, and supplied alongside the original, users could choose to read the "simple", "standard", or "advanced" page of each subject.
:*The "Simple" could be written as if talking to someone with little technical knowledge of programming. Lane out as a step by step tutorial.
:*The "Standard" would remain pretty much as they are now.
:*The "Advanced" could be written in a more terse tech heavy way, nailing the specifics and leaving out the fluff.
:Anyway; I'm not really around so much these days, so my input isn't perhaps very suitable (but I was basically invited to comment). [[User:Fred_Gandt|'''fredgandt''']] 18:31, 7 December 2012 (PST)

::As an aside: Newbie Notes was a compromises, we had an editor who wanted to write notes for new users, name the section after himself, and maintain strict editorial control over it. It didn't go anywhere after that.
::My issue with customized layouts is that it makes finding information within the articles more difficult. Instead of jumping to the content your interested in, you have to read all of it and it's not in the same place between articles.
::As you say, deciding which content goes where is difficult when you don't know where anything about your reader. A solution could be to query the user. You would go down a list of radioboxes self reporting your knowledge in a set of compatible disciplines and it would include the required prerequisites and choose the shortest route to understanding, if not attained you could tell the system to broaden it's scope and include more information from the parallel paths. It sounds like it would be really interesting to build. Not really doable with mediawiki :(

::We are doomed to fail if we can't automate the problem, this solution just doesn't scale. We can't personalize the documentation enough. People are too unique. We risk bloating the documentation too much or making it too large to manage.

::I don't consider it insulting but I'm not attached to the name. Can't please everyone. Maybe name it something like "The Basics"?

::As to [[User:Toady Nakamura|Toady Nakamura]]'s suggestion I'm all for it. If you want dedicated sections, give me an idea as to where and I'll put them in and add the variables to the template.

::The wiki creates an environment for breeding ideas. We need to foster that, it's why '''I'm in favor of giving [[User:Toady Nakamura|Toady Nakamura]] the go ahead'''. Without new ideas coming in, all we have is stagnation. Our audience is ever changing, if we don't change we will become more and more irrelevant to our target audience. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:24, 7 December 2012 (PST)

:::I think it would be fine to put entry notes at the top, as that is the first place one would look - and newer users tend to only look at the top... on the other hand... telling new users to look at the bottom of each page for detailed information would have the additional benefit of not changing the top of page layout for users who are familiar with the pages as they are now. So I vote for bottom of page, "Expert notes" and "Basic notes" on each page. And it would be lovely to have it in the template, then I could just go around and fix each page as I get to it. And yes, Fred, great idea to start with llSay and the easy ones! I will have more time for this project starting after Christmas and would be delighted to get going on it then! [[User:Toady Nakamura|Toady Nakamura]] 11:22, 19 December 2012 (PST)

::::With the expert/basic modifier, this sounds like a forking of the Notes Section, that the notes section should be retired and born anew as these two sections. I'll work on the templates tonight. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:00, 19 December 2012 (PST)

== llHTTPResponse: ==

Hey Strife,
your last edit on [[LlHTTPResponse]] didn't turn out as expected. The hover text doesn't show. I'd have changed it, but not sure how. -- [[User:Kireji Haiku|Kireji]] 08:11, 9 December 2012 (PST)

:It's working for me. What browser are you using? Are we talking about the hover in the description or for the wikipedia link? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 08:24, 14 December 2012 (PST)

::I'm on Firefox 17.0.1 on Windows 7 x64 Ultimate. -- '''[[User:Kireji Haiku|Kireji]]''' ([[User talk:Kireji_Haiku|talk]]|[[Special:Contributions/Kireji_Haiku|contribs]]) 08:20, 1 January 2013 (PST)

:::I'll take a look at it down stairs (I have the same setup down there) tomorrow if I have the time -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 23:17, 1 January 2013 (PST)

==IM via Wiki?==
Hello Strife. Is there any private Instant Messaging facility in SL Wiki? [[User:Omei Qunhua|Omei Qunhua]] 03:13, 27 December 2012 (PST)

:Nope but you can always IM me on [http://www.sluniverse.com/php/vb/members/strife.html SL Universe] or email my gmail address blindwander. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:42, 27 December 2012 (PST)

== Caveats in page LlGetAlpha are wrong. ==

Hi,
can you maybe correct the Caveats in https://wiki.secondlife.com/wiki/LlGetAlpha
It says "If face indicates a face that does not exist the return is 0.0" which is incorrect, it always returns 1.0, see also https://jira.secondlife.com/browse/BUG-1256
I couldn't find out how to change it myself: )

: I've fixed it. I'll add it to the work queue to write some documentation for the [[Template:LSL Function/face]]. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:39, 5 January 2013 (PST)

== New version of file not showing for me... ==

Hiya, so I uploaded a new version of <code>File:Lsl_syntax_for_notepad_plus_plus.png</code> and it doesn't show on [[User:Kireji Haiku/Notepad++_Syntax_Highlight|the page where I put it]]. What did I do wrong? -- [[User:Kireji Haiku|Kireji Haiku]] 09:59, 6 March 2013 (PST)

:Maybe it's your browser cache? The wiki likely isn't telling your browser that the image is stale. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 11:34, 11 March 2013 (PDT)

::I moved the content to Github. To answer your question, the old version stayed even after clearing cache. Not sure why, though. [[User:Kireji Haiku|Kireji Haiku]] 07:52, 2 May 2013 (PDT)

== GeSHi for LSL on the wiki: ==

Ok, I'll try to keep the story short. I tried contacting Torley, but he [http://wiki.secondlife.com/wiki/Project:About?diff=1173232&oldid=1146125 is not on the wiki team anymore], then I tried contacting Jeremy who seems to [[User_talk:Torley_Linden|have chosen to ignore the issue for more than half a year]]. I'm talking about the LSL syntax highlight on this wiki. I've found that this works over GeSHi and the mediawiki plugin. I contacted them there and provided a fix. Then was told I should provide the fix to GeSHi directly since it's third party software from their point of view. I provided the GeSHi team with a fix, too. Nobody really seems to be responsible for anything. So how do I get [https://github.com/buildersbrewery/lsl-for-geshi this up-to-date] file wherever so that syntax highlight is up-to-date on this particular wiki rather tomorrow than next year. [[User:Kireji Haiku|Kireji Haiku]] 07:53, 2 May 2013 (PDT)

:Yeah I don't have a good answer for you, years ago I decided to just use a greasemonkey script to add the missing coloring. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 19:20, 7 May 2013 (PDT)

::Ok, so...what do we do now? I've got a couple of highlighting files for LSL on [https://github.com/buildersbrewery?tab=repositories this github project page], which should all be up-to-date AFAIK. Do you want to work on this, or should I? If you want me to do it, let me know what I need. Maybe a copy of that greasemonkey script? [[User:Kireji Haiku|Kireji Haiku]] 02:32, 8 May 2013 (PDT)

:::It's a client side thing. http://userscripts.org/scripts/review/28162 -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:54, 9 May 2013 (PDT)

::::I'll take a look and see what I can do, thanks. [[User:Kireji Haiku|Kireji Haiku]] 00:13, 15 May 2013 (PDT)

:::::This is what I got now. I removed the lslwiki parts, though. Could you test this?

<javascript>// ==UserScript==
// @name LSL Highlighter
// @namespace http://home.comcast.net/~mailerdaemon
// @include http://wiki.secondlife.com/*
// @include https://wiki.secondlife.com/*
// @version 1
// ==/UserScript==

(function(){
var GM_addStyle = function(css){
style = document.createElement("style");
style.type = "text/css";
style.innerHTML = css;
document.getElementsByTagName('head')[0].appendChild(style);
return style;//default GM_addStyle doesn't return the new style element
};

var search = "";
var prefixed = false;

if (($X("//meta[@name='generator' and starts-with(@content,'MediaWiki ')]")))
{
GM_addStyle("table.diff td div {overflow:visible;} pre.code a{ text-decoration:none; }");
GM_addStyle(".pBody { padding:0pt 0.8em 0.3em 0.5em; border:1px solid #AAAAAA; } .portlet h5 {background: transparent;}");
prefixs = ["", "/wiki/Special:Search?search="];
search = "//pre[@class='code' or @class='lsl']";

if ((breadcrumbs = $X("//div[@id='contentSub']")))
{
if (!(title = unsafeWindow.realTitleText))
if (title = $X("//div[@id='ReatTitleBanner']/span[@id='RealTitle']"))
title = title.textContent;
if (title && unsafeWindow.wgTitle)
$Z(".//text()[contains(.,'"+unsafeWindow.wgTitle+"')]",function(r,i,p){
r.data = r.data.replace(unsafeWindow.wgTitle, title);
}, breadcrumbs);
}

GM_addStyle([
".lsl a {font-weight: bold; text-decoration: none;}",
".lsl .imp {font-weight: bold; color: red;}",
".lsl .lsl_states {color: #801A4D;}",
".lsl .lsl_events {color: #004D80;}",
".lsl .lsl_builtin_functions {color: #820124;}",
".lsl .lsl_builtin_constants_integer {color: #1A1A80;}",
".lsl .lsl_builtin_constants_string {color: #1A4D80;}",
".lsl .lsl_builtin_constants_float {color: #4D1A80;}",
".lsl .lsl_builtin_constants_compound {color: #663366;}",
".lsl .lsl_illegal_invalid {font-weight: bold; color: #FFFFFF; background-color: #FF0000; text-decoration: line-through;}",
".lsl .lsl_illegal_deprecated {font-weight: bold; color: #FFFF00; background-color: #FF0000; text-decoration: line-through;}",
".lsl .lsl_control {color: #0000CD;}",
".lsl .lsl_types {color: #003300;}",
".lsl .co1 {color: #CD4D26;}",
".lsl .es0 {color: #CD4D26;}",
".lsl .br0 {color: #66CC66;}",
".lsl .st0 {color: #003300;}",
".lsl .nu0 {color: #cc66cc;}",
".lsl .me1 {color: #006600;}",
".lsl .me2 {color: #006600;}",
""].join("\n"));
}
else
return;

function Group(className, prefix, expression, captures, processor){ this.c = className; this.v = prefix; this.r = expression; this.captures = captures || 0; this.processor = processor;}
Group.prototype = { toString: function(){ return "("+this.r+")"; }, };

var groups = [ //{
new Group("nu0", -1, "0[xX][0-9a-fA-F]+|\\.[0-9]*[Ee][+-]?[0-9]*|[0-9]+[Ee][+-]?[0-9]*"),
new Group("lsl_illegal_deprecated", 0, "ll(?:Cloud|CollisionSprite|GodLikeRezObject|Make(?:Explosion|Fountain|Smoke|Fire)|(?:Stop)?PointAt|(?:(?:Refresh|Set)Prim)URL|(?:Take|Release)Camera|RemoteDataSetRegion|RemoteLoadScript|SetInventoryPermMask|SetObjectPermMask|Sound(?:Preload)?|XorBase64Strings)|AGENT|ATTACH_[LR]PEC|CHARACTER_MAX_ANGULAR_(?:ACCEL|SPEED)|OBJECT_ATTACHMENT_(?:GEOMETRY_BYTES|SURFACE_AREA)|DATA_RATING|LAND_(?:LARGE|MEDIUM|SMALL)_BRUSH|PERMISSION_(?:CHANGE_(?:JOINTS|PERMISSIONS)|RELEASE_OWNERSHIP|REMAP_CONTROLS)|PRIM_(?:CAST_SHADOWS|MATERIAL_LIGHT|PHYSICS_MATERIAL|TYPE_LEGACY)|PSYS_SRC_(?:(?:INNER|OUTER)ANGLE|OBJ_REL_MASK)|VEHICLE_FLAG_NO_FLY_UP"),
new Group("lsl_illegal_invalid", 0, "event|print"),
new Group("lsl_states", 0, "(?:state)\\s+\\w+|default"),
new Group("lsl_control", 0, "@|do|else(?: if)?|for|if|jump|return|while"),
new Group("lsl_types", 0, "float|integer|key|list|quaternion|rotation|string|vector"),
new Group("lsl_events", 0, "(?:state_(?:entry|exit)|touch(?:_(?:start|end))?|(?:land_)?collision(?:_(?:start|end))?|timer|listen|(?:no_)?sensor|control|(?:not_)?at_(?:rot_)?target|money|email|run_time_permissions|changed|attach|dataserver|moving_(?:start|end)|link_message|(?:on|object)_rez|remote_data|http_re(?:sponse|quest)|path_update|transaction_result)"),
new Group("lsl_builtin_constants_integer", 1, "FALSE|TRUE|(?:JSON_APPEND|STATUS_(?:PHYSICS|ROTATE_[XYZ]|PHANTOM|SANDBOX|BLOCK_GRAB(?:_OBJECT)?|(?:DIE|RETURN)_AT_EDGE|CAST_SHADOWS|OK|MALFORMED_PARAMS|TYPE_MISMATCH|BOUNDS_ERROR|NOT_(?:FOUND|SUPPORTED)|INTERNAL_ERROR|WHITELIST_FAILED)|AGENT(?:_(?:BY_(?:LEGACY_|USER)NAME|FLYING|ATTACHMENTS|SCRIPTED|MOUSELOOK|SITTING|ON_OBJECT|AWAY|WALKING|IN_AIR|TYPING|CROUCHING|BUSY|ALWAYS_RUN|AUTOPILOT|LIST_(?:PARCEL(?:_OWNER)?|REGION)))?|CAMERA_(?:PITCH|DISTANCE|BEHINDNESS_(?:ANGLE|LAG)|(?:FOCUS|POSITION)(?:_(?:THRESHOLD|LOCKED|LAG))?|FOCUS_OFFSET|ACTIVE)|ANIM_ON|LOOP|REVERSE|PING_PONG|SMOOTH|ROTATE|SCALE|ALL_SIDES|LINK_(?:ROOT|SET|ALL_(?:OTHERS|CHILDREN)|THIS)|ACTIVE|PASSIVE|SCRIPTED|CONTROL_(?:FWD|BACK|(?:ROT_)?(?:LEFT|RIGHT)|UP|DOWN|(?:ML_)?LBUTTON)|PERMISSION_(?:RETURN_OBJECTS|DEBIT|OVERRIDE_ANIMATIONS|SILENT_ESTATE_MANAGEMENT|TAKE_CONTROLS|TRIGGER_ANIMATION|ATTACH|CHANGE_LINKS|(?:CONTROL|TRACK)_CAMERA|TELEPORT)|INVENTORY_(?:TEXTURE|SOUND|OBJECT|SCRIPT|LANDMARK|CLOTHING|NOTECARD|BODYPART|ANIMATION|GESTURE|ALL|NONE)|CHANGED_(?:INVENTORY|COLOR|SHAPE|SCALE|TEXTURE|LINK|ALLOWED_DROP|OWNER|REGION(?:_START)?|TELEPORT|MEDIA)|OBJECT_(?:(?:PHYSICS|SERVER|STREAMING)_COST|UNKNOWN_DETAIL|CHARACTER_TIME|PHANTOM|PHYSICS|TEMP_ON_REZ|NAME|DESC|POS|PRIM_EQUIVALENCE|RETURN_(?:PARCEL(?:_OWNER)?|REGION)|ROO?T|VELOCITY|OWNER|GROUP|CREATOR|ATTACHED_POINT|RENDER_WEIGHT|PATHFINDING_TYPE|(?:RUNNING|TOTAL)_SCRIPT_COUNT|SCRIPT_(?:MEMORY|TIME))|TYPE_(?:INTEGER|FLOAT|STRING|KEY|VECTOR|ROTATION|INVALID)|(?:DEBUG|PUBLIC)_CHANNEL|ATTACH_(?:AVATAR_CENTER|CHEST|HEAD|BACK|PELVIS|MOUTH|CHIN|NECK|NOSE|BELLY|[LR](?:SHOULDER|HAND|FOOT|EAR|EYE|[UL](?:ARM|LEG)|HIP)|(?:LEFT|RIGHT)_PEC|HUD_(?:CENTER_[12]|TOP_(?:RIGHT|CENTER|LEFT)|BOTTOM(?:_(?:RIGHT|LEFT))?))|LAND_(?:LEVEL|RAISE|LOWER|SMOOTH|NOISE|REVERT)|DATA_(?:ONLINE|NAME|BORN|SIM_(?:POS|STATUS|RATING)|PAYINFO)|PAYMENT_INFO_(?:ON_FILE|USED)|REMOTE_DATA_(?:CHANNEL|REQUEST|REPLY)|PSYS_(?:PART_(?:BF_(?:ZERO|ONE(?:_MINUS_(?:DEST_COLOR|SOURCE_(ALPHA|COLOR)))?|DEST_COLOR|SOURCE_(ALPHA|COLOR))|BLEND_FUNC_(DEST|SOURCE)|FLAGS|(?:START|END)_(?:COLOR|ALPHA|SCALE|GLOW)|MAX_AGE|(?:RIBBON_|WIND|INTERP_(?:COLOR|SCALE)|BOUNCE|FOLLOW_(?:SRC|VELOCITY)|TARGET_(?:POS|LINEAR)|EMISSIVE)_MASK)|SRC_(?:MAX_AGE|PATTERN|ANGLE_(?:BEGIN|END)|BURST_(?:RATE|PART_COUNT|RADIUS|SPEED_(?:MIN|MAX))|ACCEL|TEXTURE|TARGET_KEY|OMEGA|PATTERN_(?:DROP|EXPLODE|ANGLE(?:_CONE(?:_EMPTY)?)?)))|VEHICLE_(?:REFERENCE_FRAME|TYPE_(?:NONE|SLED|CAR|BOAT|AIRPLANE|BALLOON)|(?:LINEAR|ANGULAR)_(?:FRICTION_TIMESCALE|MOTOR_DIRECTION)|LINEAR_MOTOR_OFFSET|HOVER_(?:HEIGHT|EFFICIENCY|TIMESCALE)|BUOYANCY|(?:LINEAR|ANGULAR)_(?:DEFLECTION_(?:EFFICIENCY|TIMESCALE)|MOTOR_(?:DECAY_)?TIMESCALE)|VERTICAL_ATTRACTION_(?:EFFICIENCY|TIMESCALE)|BANKING_(?:EFFICIENCY|MIX|TIMESCALE)|FLAG_(?:NO_DEFLECTION_UP|LIMIT_(?:ROLL_ONLY|MOTOR_UP)|HOVER_(?:(?:WATER|TERRAIN|UP)_ONLY|GLOBAL_HEIGHT)|MOUSELOOK_(?:STEER|BANK)|CAMERA_DECOUPLED))|PRIM_(?:TYPE(?:_(?:BOX|CYLINDER|PRISM|SPHERE|TORUS|TUBE|RING|SCULPT))?|HOLE_(?:DEFAULT|CIRCLE|SQUARE|TRIANGLE)|MATERIAL(?:_(?:STONE|METAL|GLASS|WOOD|FLESH|PLASTIC|RUBBER))?|SHINY_(?:NONE|LOW|MEDIUM|HIGH)|BUMP_(?:NONE|BRIGHT|DARK|WOOD|BARK|BRICKS|CHECKER|CONCRETE|TILE|STONE|DISKS|GRAVEL|BLOBS|SIDING|LARGETILE|STUCCO|SUCTION|WEAVE)|TEXGEN_(?:DEFAULT|PLANAR)|SCULPT_(?:TYPE_(?:SPHERE|TORUS|PLANE|CYLINDER|MASK)|FLAG_(?:MIRROR|INVERT))|PHYSICS(?:_(?:SHAPE_(?:CONVEX|NONE|PRIM|TYPE)))?|(?:POS|ROT)_LOCAL|SLICE|TEXT|FLEXIBLE|POINT_LIGHT|TEMP_ON_REZ|PHANTOM|POSITION|SIZE|ROTATION|TEXTURE|NAME|OMEGA|DESC|LINK_TARGET|COLOR|BUMP_SHINY|FULLBRIGHT|TEXGEN|GLOW|MEDIA_(?:ALT_IMAGE_ENABLE|CONTROLS|(?:CURRENT|HOME)_URL|AUTO_(?:LOOP|PLAY|SCALE|ZOOM)|FIRST_CLICK_INTERACT|(?:WIDTH|HEIGHT)_PIXELS|WHITELIST(?:_ENABLE)?|PERMS_(?:INTERACT|CONTROL)|PARAM_MAX|CONTROLS_(?:STANDARD|MINI)|PERM_(?:NONE|OWNER|GROUP|ANYONE)|MAX_(?:URL_LENGTH|WHITELIST_(?:SIZE|COUNT)|(?:WIDTH|HEIGHT)_PIXELS)))|MASK_(?:BASE|OWNER|GROUP|EVERYONE|NEXT)|PERM_(?:TRANSFER|MODIFY|COPY|MOVE|ALL)|PARCEL_(?:MEDIA_COMMAND_(?:STOP|PAUSE|PLAY|LOOP|TEXTURE|URL|TIME|AGENT|UNLOAD|AUTO_ALIGN|TYPE|SIZE|DESC|LOOP_SET)|FLAG_(?:ALLOW_(?:FLY|(?:GROUP_)?SCRIPTS|LANDMARK|TERRAFORM|DAMAGE|CREATE_(?:GROUP_)?OBJECTS)|USE_(?:ACCESS_(?:GROUP|LIST)|BAN_LIST|LAND_PASS_LIST)|LOCAL_SOUND_ONLY|RESTRICT_PUSHOBJECT|ALLOW_(?:GROUP|ALL)_OBJECT_ENTRY)|COUNT_(?:TOTAL|OWNER|GROUP|OTHER|SELECTED|TEMP)|DETAILS_(?:NAME|DESC|OWNER|GROUP|AREA|ID|SEE_AVATARS))|LIST_STAT_(?:MAX|MIN|MEAN|MEDIAN|STD_DEV|SUM(?:_SQUARES)?|NUM_COUNT|GEOMETRIC_MEAN|RANGE)|PAY_(?:HIDE|DEFAULT)|REGION_FLAG_(?:ALLOW_DAMAGE|FIXED_SUN|BLOCK_TERRAFORM|SANDBOX|DISABLE_(?:COLLISIONS|PHYSICS)|BLOCK_FLY|ALLOW_DIRECT_TELEPORT|RESTRICT_PUSHOBJECT)|HTTP_(?:METHOD|MIMETYPE|BODY_(?:MAXLENGTH|TRUNCATED)|CUSTOM_HEADER|PRAGMA_NO_CACHE|VERBOSE_THROTTLE|VERIFY_CERT)|STRING_(?:TRIM(?:_(?:HEAD|TAIL))?)|CLICK_ACTION_(?:NONE|TOUCH|SIT|BUY|PAY|OPEN(?:_MEDIA)?|PLAY|ZOOM)|TOUCH_INVALID_FACE|PROFILE_(?:NONE|SCRIPT_MEMORY)|RC_(?:DATA_FLAGS|DETECT_PHANTOM|GET_(?:LINK_NUM|NORMAL|ROOT_KEY)|MAX_HITS|REJECT_(?:TYPES|AGENTS|(?:NON)?PHYSICAL|LAND))|RCERR_(?:CAST_TIME_EXCEEDED|SIM_PERF_LOW|UNKNOWN)|ESTATE_ACCESS_(?:ALLOWED_(?:AGENT|GROUP)_(?:ADD|REMOVE)|BANNED_AGENT_(?:ADD|REMOVE))|DENSITY|FRICTION|RESTITUTION|GRAVITY_MULTIPLIER|KFM_(?:COMMAND|CMD_(?:PLAY|STOP|PAUSE|SET_MODE)|MODE|FORWARD|LOOP|PING_PONG|REVERSE|DATA|ROTATION|TRANSLATION)|ERR_(?:GENERIC|PARCEL_PERMISSIONS|MALFORMED_PARAMS|RUNTIME_PERMISSIONS|THROTTLED)|CHARACTER_(?:CMD_(?:(?:SMOOTH_)?STOP|JUMP)|DESIRED_(?:TURN_)?SPEED|RADIUS|STAY_WITHIN_PARCEL|LENGTH|ORIENTATION|ACCOUNT_FOR_SKIPPED_FRAMES|AVOIDANCE_MODE|TYPE(?:_(?:[ABCD]|NONE))?|MAX_(?:DECEL|TURN_RADIUS|(?:ACCEL|SPEED)))|PURSUIT_(?:OFFSET|FUZZ_FACTOR|GOAL_TOLERANCE|INTERCEPT)|REQUIRE_LINE_OF_SIGHT|FORCE_DIRECT_PATH|VERTICAL|HORIZONTAL|AVOID_(?:CHARACTERS|DYNAMIC_OBSTACLES|NONE)|PU_(?:EVADE_(?:HIDDEN|SPOTTED)|FAILURE_(?:DYNAMIC_PATHFINDING_DISABLED|INVALID_(?:GOAL|START)|NO_(?:NAVMESH|VALID_DESTINATION)|OTHER|TARGET_GONE|(?:PARCEL_)?UNREACHABLE)|(?:GOAL|SLOWDOWN_DISTANCE)_REACHED)|TRAVERSAL_TYPE(?:_(?:FAST|NONE|SLOW))?|CONTENT_TYPE_(?:ATOM|FORM|HTML|JSON|LLSD|RSS|TEXT|XHTML|XML)|GCNP_(?:RADIUS|STATIC)|(?:PATROL|WANDER)_PAUSE_AT_WAYPOINTS|OPT_(?:AVATAR|CHARACTER|EXCLUSION_VOLUME|LEGACY_LINKSET|MATERIAL_VOLUME|OTHER|STATIC_OBSTACLE|WALKABLE)|SIM_STAT_PCT_CHARS_STEPPED)"),
new Group("lsl_builtin_constants_string", 1, "(?:EOF|JSON_(?:ARRAY|DELETE|FALSE|INVALID|NULL|NUMBER|OBJECT|STRING|TRUE)|NULL_KEY|TEXTURE_(?:BLANK|DEFAULT|MEDIA|PLYWOOD|TRANSPARENT)|URL_REQUEST_(?:GRANTED|DENIED))"),
new Group("lsl_builtin_constants_float", 1, "DEG_TO_RAD|PI(?:_BY_TWO)?|RAD_TO_DEG|SQRT2|TWO_PI"),
new Group("lsl_builtin_constants_compound", 1, "ZERO_(?:ROTATION|VECTOR)|TOUCH_INVALID_(?:TEXCOORD|VECTOR)"),
new Group("lsl_builtin_functions", 0, "(?:ll(?:ReturnObjectsBy(?:ID|Owner)|Json(?:2List|[GS]etValue|ValueType)|Sin|Cos|Tan|Atan2|Sqrt|Pow|Abs|Fabs|Frand|Floor|Ceil|Round|Vec(?:Mag|Norm|Dist)|Rot(?:Between|2(?:Euler|Fwd|Left|Up))|(?:Euler|Axes)2Rot|Whisper|(?:Region|Owner)?Say|Shout|Listen(?:Control|Remove)?|Sensor(?:Repeat|Remove)?|Detected(?:Name|Key|Owner|Type|Pos|Vel|Grab|Rot|Group|LinkNumber)|Die|Ground|Wind|(?:[GS]et)(?:AnimationOverride|MemoryLimit|PrimMediaParams|ParcelMusicURL|Object(?:Desc|Name)|PhysicsMaterial|Status|Scale|Color|Alpha|Texture|Pos|Rot|Force|Torque)|ResetAnimationOverride|(?:Scale|Offset|Rotate)Texture|(?:Rot)?Target(?:Remove)?|(?:Stop)?MoveToTarget|Apply(?:Rotational)?Impulse|Set(?:KeyframedMotion|ContentType|RegionPos|(?:Angular)?Velocity|Buoyancy|HoverHeight|ForceAndTorque|TimerEvent|ScriptState|Damage|TextureAnim|Sound(?:Queueing|Radius)|Vehicle(?:Type|(?:Float|Vector|Rotation)Param)|(?:Touch|Sit)?Text|Camera(?:Eye|At)Offset|PrimitiveParams|ClickAction|Link(?:Alpha|Color|PrimitiveParams(?:Fast)?|Texture(?:Anim)?|Camera|Media)|RemoteScriptAccessPin|PayPrice|LocalRot)|Get(?:ClosestNavPoint|StaticPath|SimStats|Env|PrimitiveParams|Link(?:PrimitiveParams|Number(?:OfSides)?|Key|Name|Media)|HTTPHeader|FreeURLs|Object(?:Details|PermMask|PrimCount)|Parcel(?:MaxPrims|Details|Prim(?:Count|Owners))|Attached|(?:SPMax|Free|Used)Memory|Region(?:Name|TimeDilation|FPS|Corner|AgentCount)|Root(?:Position|Rotation)|UnixTime|(?:Parcel|Region)Flags|(?:Wall|GMT)clock|SimulatorHostname|BoundingBox|GeometricCenter|Creator|NumberOf(?:Prims|NotecardLines|Sides)|Animation(?:List)?|(?:Camera|Local)(?:Pos|Rot)|Vel|Accel|Omega|Time(?:stamp|OfDay)|(?:Object|CenterOf)?Mass|MassMKS|Energy|Owner|(?:Owner)?Key|SunDirection|Texture(?:Offset|Scale|Rot)|Inventory(?:Number|Name|Key|Type|Creator|PermMask)|Permissions(?:Key)?|StartParameter|List(?:Length|EntryType)|Date|Agent(?:Size|Info|Language|List)|LandOwnerAt|NotecardLine|Script(?:Name|State))|(?:Get|Reset|GetAndReset)Time|PlaySound(?:Slave)?|LoopSound(?:Master|Slave)?|(?:Trigger|Stop|Preload)Sound|(?:(?:Get|Delete)Sub|Insert)String|To(?:Upper|Lower)|Give(?:InventoryList|Money)|RezObject|(?:Stop)?LookAt|Sleep|CollisionFilter|(?:Take|Release)Controls|DetachFromAvatar|AttachToAvatar(?:Temp)?|InstantMessage|(?:GetNext)?Email|StopHover|MinEventDelay|RotLookAt|String(?:Length|Trim)|(?:Start|Stop)Animation|TargetOmega|RequestPermissions|(?:Create|Break)Link|BreakAllLinks|(?:Give|Remove)Inventory|Water|PassTouches|Request(?:Agent|Inventory)Data|TeleportAgent(?:Home|GlobalCoords)?|ModifyLand|CollisionSound|ResetScript|MessageLinked|PushObject|PassCollisions|AxisAngle2Rot|Rot2(?:Axis|Angle)|A(?:cos|sin)|AngleBetween|AllowInventoryDrop|SubStringIndex|List2(?:CSV|Integer|Json|Float|String|Key|Vector|Rot|List(?:Strided)?)|DeleteSubList|List(?:Statistics|Sort|Randomize|(?:Insert|Find|Replace)List)|EdgeOfWorld|AdjustSoundVolume|Key2Name|TriggerSoundLimited|EjectFromLand|(?:CSV|ParseString)2List|OverMyLand|SameGroup|UnSit|Ground(?:Slope|Normal|Contour)|GroundRepel|(?:Set|Remove)VehicleFlags|(?:AvatarOn)?(?:Link)?SitTarget|Script(?:Danger|Profiler)|Dialog|VolumeDetect|ResetOtherScript|RemoteLoadScriptPin|(?:Open|Close)RemoteDataChannel|SendRemoteData|RemoteDataReply|(?:Integer|String)ToBase64|XorBase64|Log(?:10)?|Base64To(?:String|Integer)|ParseStringKeepNulls|RezAtRoot|RequestSimulatorData|ForceMouselook|(?:Load|Release|(?:E|Une)scape)URL|ParcelMedia(?:CommandList|Query)|ModPow|MapDestination|(?:RemoveFrom|AddTo|Reset)Land(?:Pass|Ban)List|(?:Set|Clear)CameraParams|HTTP(?:Request|Response)|TextBox|DetectedTouch(?:UV|Face|Pos|(?:N|Bin)ormal|ST)|(?:MD5|SHA1|DumpList2)String|Request(?:Secure)?URL|Clear(?:Prim|Link)Media|(?:Link)?ParticleSystem|(?:Get|Request)(?:Username|DisplayName)|RegionSayTo|CastRay|GenerateKey|TransferLindenDollars|ManageEstateAccess|(?:Create|Delete)Character|ExecCharacterCmd|Evade|FleeFrom|NavigateTo|PatrolPoints|Pursue|UpdateCharacter|WanderWithin))"),
]; //}
const gl = groups.length;
var missed = new RegExp("^(|[\\W\\w]*?\\W)("+groups.join("|")+")([\\W][\\W\\w]*|)$");

var lang = $X("//div[@id='PageLanguage']");
lang = (lang && lang.innerHTML) || "";

$Z(search, function(r,i){
for (var a = 0; b = r.childNodes[a]; ++a)
if (b.nodeName == "#text" && (c = missed.exec(b.nodeValue)))
{
var s, v, p, q;
if ((v = c[c.length - 1]) && (v != ""))//whitespace after
insertAfter(document.createTextNode(v), b);
for (p=0, q = 3; p < gl; p++)
{
var n = groups[p];
var y = 1 + n.captures;
if ((v = c[q]) && (v != ""))
{
if (n.v >= 0)
{
s = document.createElement("a");
s.href = prefixs[n.v] + v + lang;
}
else
s = document.createElement("span");
if (n.c && n.c != "")
s.className = n.c;
s.appendChild(document.createTextNode(v));
insertAfter(s, b);
if (!(v = c[1]) || (v == ""))//whitespace before
b.parentNode.removeChild(b);
else
b.nodeValue = c[1];
if (n.processor)
n.processor(s, c.slice(q, q + y), c[1], c[c.length - 1]);
break;
}
q += y;
}
}
if ((b = r.childNodes[0]) && b.nodeName == "#text" && b.nodeValue.substring(0,7) == " \n")
b.nodeValue = b.nodeValue.substring(7);
if ((b = r.childNodes[r.childNodes.length - 1]) && b.nodeName == "#text" && b.nodeValue.substr(-2) == "\n ")
b.nodeValue = b.nodeValue.substring(0, b.nodeValue.length - 2);
if (lang) $Z("./a[span[starts-with(@class,'kw')]]", function(ir,ii){ir.attributes.getNamedItem("href").value += lang;}, r);
});

$Z("//a[starts-with(@title, 'Ll') and starts-with(@title, text())]", function(r,i){
var m = "l" + r.title.substring(1);
if (r.title == r.innerHTML)
r.innerHTML = m;
r.title = m;
});

if (m = $X("//li[@id='n-editingdiscussion']")){
n = document.createElement("li");
n.id = "n-randompage";
n.innerHTML = "<a accesskey='x' title='Load a random article [alt-shift-x]' href='/wiki/Special:Random'>Random Page</a>";
insertAfter(n, m);
}

function $X(_xpath, node){
var doc = (node)?(node.ownerDocument || node):(node = document);
return doc.evaluate(_xpath, node, null, XPathResult.ORDERED_NODE_SNAPSHOT_TYPE, null).snapshotItem(0);
}
function $Z(_xpath, func, node){
var doc = (node)?(node.ownerDocument || node):(node = document);
var res = doc.evaluate(_xpath, node, null, XPathResult.ORDERED_NODE_SNAPSHOT_TYPE, null);
var args = Array.prototype.slice.call(arguments, 3);
var i = 0;
for (; i < res.snapshotLength; ++i)
func.apply(func, [res.snapshotItem(i), i].concat(args));
return i;
}
function insertAfter(insert, after){return after.parentNode.insertBefore(insert, after.nextSibling);}
function insertBefore(insert, before){return before.parentNode.insertBefore(insert, before);}
function log(){
var arg;
switch (arguments.length) {
case 1:
arg = arguments[0];
break;
case 0:
arg = null;
break;
default:
arg = arguments;
break;
}

if (typeof(unsafeWindow.console) != "undefined" && typeof(unsafeWindow.console.log) != "undefined")
unsafeWindow.console.log(arg);
else if (typeof(GM_log) != "undefined")
GM_log(arg);
return arg;
}
})();</javascript>

Cheers! [[User:Kireji Haiku|Kireji Haiku]] 11:49, 22 May 2013 (PDT)

:I had to make all the sub-expressions use non-capture groups (which was how it was originally). I also made some minor tweaks that should do nothing but are for style correctness (I've learned better JS habits since I wrote that). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 14:44, 22 May 2013 (PDT)

:I've added support for custom post-processing for groups and for them capture information from the expression. If we decide to merge bad numbers into a single node, that code would be a post-processor. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 00:18, 23 May 2013 (PDT)

::Whatever works I'd say. Not sure why you chose purple for numbers, though. Did you test it? Where to put this now? [[User:Kireji Haiku|Kireji Haiku]] 13:27, 23 May 2013 (PDT)

:::Purple because that's the color they are now and it makes highlighting look right on pages like [[float]]. I usually post these to [UserScripts.org] (which I have just [http://userscripts.org/scripts/review/28162 done]) and let people find them on their own. Sometime I'll post a forum thread about them, but I haven't done that in ages. I'm hoping that is what you meant. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:52, 23 May 2013 (PDT)

::::No, I meant are you going to upload it to the wiki here so the highlighting here is fixed. Or how does this work? Have a nice weekend [[User:Kireji Haiku|Kireji Haiku]] 08:17, 24 May 2013 (PDT)

:::::Oh dear, I was afraid of this at the last. It's a script for {{Wikipedia|Greasemonkey|w=n}}, it's not a server script. It probably will work in Chrome as well (not tested). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 10:33, 24 May 2013 (PDT)

::Ok, so this brings us back to GeSHi? How to update that? [[User:Kireji Haiku|Kireji Haiku]] 12:19, 27 May 2013 (PDT)

:::The only way to do so is likely to be pestering LL. At this point I don't know who you would start with. Couldn't hurt to open a new bug on Jira, something along the lines of "LSL Syntax highlighting on the wiki needs updating" and see which linden is foolish enough to update the jira. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 19:22, 27 May 2013 (PDT)

== kwdb ==

By the way, there's a LSL keywords database that generates output for various syntax highlighters including GeSHi [http://code.google.com/p/kwdb/ here]. -- [[User:Sei Lisa|Sei Lisa]] 09:12, 4 June 2013 (PDT)

:Thanks for the info. It's not that I don't have a file, I don't know where to put it so the syntax highlighting works on this wiki. I've got a copy I'm working on myself on [https://github.com/buildersbrewery/lsl-for-geshi github.com/buildersbrewery/lsl-for-geshi]. -- [[User:Kireji Haiku|Kireji Haiku]] 09:40, 5 June 2013 (PDT)

::LL has to install it in some directory on the server (they will know if they look for where the old one is), it's not something we can do. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 11:14, 5 June 2013 (PDT)

:You may be interested in https://github.com/pclewis/lslint/commits/23c3fb11226249f633bed1f0b077435e58f80781/wiki_builtins.pl it's a script to walk the wiki to get functions, events and constants. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 11:14, 5 June 2013 (PDT)

::Thank you. That script generates some "false positives" and lacks some constants. Currently the generator provides also lslint output, by the way. Most other collections of keywords I've evaluated are incomplete and sometimes incorrect, and I try to keep it up to date. For example, Kireji's list misses some OBJECT_* constants and has other problems. -- [[User:Sei Lisa|Sei Lisa]] 12:51, 7 June 2013 (PDT)

:::I know it lacks some constants, I don't always remember to add them to the signature section. False positives? That is surprising. Could you give me an example? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:23, 7 June 2013 (PDT)

::::I wouldn't be surprised if it comes up with a few functions that it shouldn't. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:48, 7 June 2013 (PDT)

:::::Sorry, false positive, singular. CLICK_ACTION_ZOOM doesn't exist. Some constants come out duplicated, some list wrong values. Here's a diff if interested. http://pastebin.ca/2393166 -- [[User:Sei Lisa|Sei Lisa]] 05:23, 8 June 2013 (PDT)

::::::That diff really helps. It suggests we have several wrong values here on the wiki and gives us a good place to start fixing things. However I don't think it's a good idea for the wiki to move away from hex notation just so that we match the source code, not all of the LSL Portal's readers know their powers of two. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:40, 8 June 2013 (PDT)

::::::P.S. I consider the duplicates a bug in the script. Yes some constants appear in multiple articles signature section, it's a <strike>hack</strike> feature.

:::::::I'm not going to login to test this are you sure there is no CLICK_ACTION_ZOOM? https://bitbucket.org/lindenlab/viewer-release/src/41898042294e4c48d9fc8bbc327f0926ed6b6712/indra/lscript/lscript_compile/indra.l#cl-644 If it's not valid than you have found a bug. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 23:00, 8 June 2013 (PDT)

::::::::I'm completely sure. What do you mean about hex notation? In the database, my criterion is to write in hex the numbers that are supposed to be bitfields, as that's the closest to binary that LSL supports. Nothing to do with the source code. That generates some differences between wiki and kwdb that are not real differences, you can just ignore them. I processed the files in order to make them comparable, including removing the arg names and removing leading zeros from hex numbers, but not transforming them to a common base, thus differences in radix are expected. -- [[User:Sei Lisa|Sei Lisa]] 08:19, 9 June 2013 (PDT)

:::::::::I just meant some integer constants had values like 0x80 or 128. I hadn't considered parameter name changes but we do use different names for the parameters (some of the original parameter names are confusing or poorly chosen). As you say not real differences. I'll file a bug about CLICK_ACTION_ZOOM, they must have forgotten to put it in the server side compiler. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 00:12, 10 June 2013 (PDT)

::::::::::{{JIRA|BUG-2827}} -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 01:15, 10 June 2013 (PDT)

:::::::::::Thanks for the link, but it's useless for mortals. -- [[User:Sei Lisa|Sei Lisa]] 07:49, 10 June 2013 (PDT)

::::::::::::Ah I forgot about that problem. It's basically a duplicate of {{Jira|SCR-236}}. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 11:25, 10 June 2013 (PDT)

:::::::::I'll also start working on the real conflicts. Thanks for taking the time. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 01:21, 10 June 2013 (PDT)

::::::::::I figured you meant 0xNNN but I don't understand why you said it's not a good idea to move away from hex notation, as I didn't remotely suggest that. Some constants that are in decimal in the wiki are in hex in kwdb, like some RC_* ones, and vice versa, like CONTENT_TYPE_*. There are a few where it can be debatable whether they are flags, like ESTATE_ACCESS_* (which is not specified to support multiple flags, though the header says "action flag") and PSYS_SRC_PATTERN_* of which you can't combine several, to my knowledge, so I considered they should not be regarded as flags. -- [[User:Sei Lisa|Sei Lisa]] 04:54, 10 June 2013 (PDT)

::::::::::PSYS_SRC_PATTERN_* was probably built rather than designed (that is to say, they hadn't entirely decided what they were doing when they did it). It will require some testing but it makes sense to allow the combining of (ALLOWED_AGENT_ADD | BANNED_AGENT_REMOVE) or (ALLOWED_AGENT_REMOVE | BANNED_AGENT_ADD), LL may have laid out the constants with that in mind even if they never added support for it. Or the number correspond with internal constants the server uses, and the server combines them. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 11:25, 10 June 2013 (PDT)

::::What about the "other problems"? -- [[User:Kireji Haiku|Kireji Haiku]] 10:35, 8 June 2013 (PDT)

I've updated the float constants to use the values from https://bitbucket.org/lindenlab/viewer-release/src/41898042294e4c48d9fc8bbc327f0926ed6b6712/indra/llmath/llmath.h?at=default#cl-56 -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 12:09, 10 June 2013 (PDT)

:KFM_CMD_SET_MODE what is it used for? PSYS_SRC_OBJ_REL_MASK is a dead constant. Used for nothing.
:I can see why you would be confused, most of those where the radix differs is in the direction of more obscure.
:-- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 13:52, 10 June 2013 (PDT)

::I don't know what it's used for. I know it's defined, as it passed the constant values test. If it's unused, its status in the database should be marked as unimplemented. PSYS_SRC_OBJ_REL_MASK was already marked as such. Output modules for LSL2dfg/kwdb can choose to skip these or put them in a separate section of the generated output if they wish, based on the status field. I'm pondering whether it would make sense to define a new status, "unknown", for KFM_CMD_SET_MODE. -- [[User:Sei Lisa|Sei Lisa]] 15:57, 10 June 2013 (PDT)

:::I'll have to spend some time figuring out how I'm going to document these (and those PRIM_MEDIA_* flags I never documented because I thought LL would remove them {{JIRA|VWR-24413}}). I think we need a category for useless and nearly useless constants constants. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:31, 10 June 2013 (PDT)

:::P.S. [[Release_Notes/Second_Life_RC_BlueSteel/13]]

== [edit][edit][edit] ==

Hello strife,
I recently made changes on the Lag-page, and today I noticed that the "Cache" section (which I've added) shows the [edit] link three times!
Could you please help me fixing this, I have no clue what I did wrong (again) https://wiki.secondlife.com/wiki/Lag :D Thanks!

:You didn't do anything wrong per se. It's a design defect of how CSS "float" works (more preciesly the defect is with the scope of "clear"). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:06, 14 June 2013 (PDT)

::Just leaving a thank you! --[[User:MartinRJ Fayray|MartinRJ Fayray]] 10:29, 15 June 2013 (PDT)

== Pathfinding categories ==

I've found that the pathfinding categories are somewhat messed up. There's [[:Category:Pathfinding]] and [[:Category:LSL Pathfinding]]. [[llGetSimStats]] is only in the latter, as is the case for some <code>CHARACTER_*</code> constants. I think there should be a "single stop" page (category) for them. Do you agree? If so, which one do you think it should be? --[[User:Pedro Oval|Pedro Oval]] 12:47, 29 August 2013 (PDT)

:I do in deed agree but I also don't like to break the naming tradition or trash a Linden category. But since you suggested it, we should probably do away with one of the categories. Any thoughts as to which one? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 14:37, 29 August 2013 (PDT)

::The description in [[:Category:Pathfinding]] reads: "Articles related to new pathfinding feature and related LSL API." Maybe the LSL API part should be moved to its own [[:Category:LSL_Pathfinding]] and leave '''Pathfinding''' for articles only (and include '''LSL_Pathfinding''' as a subcategory of it). I think that makes the most sense. People who linked to '''Pathfinding''' will find the link to the LSL one. --[[User:Pedro Oval|Pedro Oval]] 17:03, 29 August 2013 (PDT)

:::Works for me. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:33, 29 August 2013 (PDT)

::::Done. Please review what I've done, I'm not too confident to have gotten it right. I used the template name <nowiki>{{Pathfinding LSL alpha}}</nowiki> to switch the template while respecting the original intention. The name has Pathfinding at the start (as opposed to LSL Pathfinding Alpha) for emphasis on Pathfinding. While on it, I also renamed Template:LSL_Constants/llWanderW'''I'''thin to the right case. --[[User:Pedro Oval|Pedro Oval]] 08:41, 30 August 2013 (PDT)

:::::Good catch. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 09:50, 30 August 2013 (PDT)

== [[Template:LSL_Header]] ==
I believe it could use a link to [[LSL_Alternate_Editors]]. Whatcha think? -- [[User:Kireji Haiku|Kireji Haiku]] 10:16, 8 October 2013 (PDT)

:See [[Template_talk:LSL_Header]] for my reply. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 14:37, 8 October 2013 (PDT)

== Broken links: ==
On [[User:Strife Onizuka|your user page]] in the Scite/ESL section all links to your comcast account are broken. Oh yeah and...it was C++. -- [[User:Kireji Haiku|Kireji Haiku]] 07:43, 16 October 2013 (PDT)

:yes they are. I'll look into finding a place to host them. I knew C had changed a lot since I learned it but I didn't think they added member functions. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 11:15, 16 October 2013 (PDT)

::I've just updated my links and uploaded everything. I've even published the most up to date and complete lsl.api (it's an an export of kwdb). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 17:31, 16 October 2013 (PDT)

== German translation of llList2Json ==

Hiya Strife,
I just made an attempt to start translating the JSON functions to German,
but this page shows me a weird error message, could you please tell me what I did wrong :P
[[LlList2Json/de]] {{Unsigned|MartinRJ Fayray}}

:'n Abend, ich denke ich hab den Fehler behoben, Du hattest wohl einen senkrechten Strich ganz am Anfang zu viel. And yeah, Strife... I think I fixed it, there was a pipe too many. Not sure about the fix though, so if the fix needs a fix, have a go at it, LOL. Anyhow, enjoy the weekend you two. -- [[User:Kireji Haiku|Kireji Haiku]] 15:06, 18 October 2013 (PDT)

::Oops, thanks Kireji : ) --[[User:MartinRJ Fayray|MartinRJ Fayray]] 15:32, 18 October 2013 (PDT)

:I'll work on updating the [[Template:LSL Function/de]] (I generally do not update the templates for other languages). My view on the entire thing has to do with knowing your audience, each language represents a group of distinct cultures, who each have different cultural norms rooted deep in history. I would not presume to force the same layout on everyone (only English speakers). Also some of the template features for example do not work for Japaense. But to get back on topic. I don't want people to feel that English is the only language. I really want the international community to come and own their part of the wiki, figure out what works and doesn't. My goal is only to provide a framework, give them something to start from. There is no reason the articles need to be literal translations, and we gain nothing by having them be so.

:As to what is wrong with the template, it never got updated beyond the point where LL stopped adding functions to LSO. It assumes all functions have ids. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:53, 18 October 2013 (PDT)

:I'm going to update the template but someone will need to go through and translate it. It hasn't been updated in 5 years so it's going to be a bumpy ride but hey you get 5 years worth of template insanity all at once instead of gradually. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:20, 18 October 2013 (PDT)

::Thanks, that's great =) --[[User:MartinRJ Fayray|MartinRJ Fayray]] 22:31, 18 October 2013 (PDT)

:::There are a few templates that need translating, here is what i've got so far (I'll add more as I find them): - '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 22:46, 18 October 2013 (PDT)
:::[[Template:LSL_Bug_Icon/en]] -> [[Template:LSL_Bug_Icon/de]]
:::[[Template:LSL_Generic/Issues]] -> [[Template:LSL_Generic/Issues/de]]
:::[[Template:LSL_Generic/Caveats]] -> [[Template:LSL_Generic/Caveats/de]]

:::Discovered the header template was broken. Was just easier to port. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 23:21, 18 October 2013 (PDT)

:::There are likely other templates that need updating to work with the newer version of the template. Let me know if you encounter a broken template. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 23:24, 18 October 2013 (PDT)

::::I translated the 3 above templates, but on the article page [[LlList2Json/de]] the "Caveats" and "Jira Search" sections are still using the English template. Thanks so far, though : ) Also these headlines should also be translated: "Specification" = "Beschreibung", "Caveats" = "Anmerkungen", "Examples" = "Beispiele", "See Also" = "Siehe auch", "Deep Notes" = "Erweitert" --[[User:MartinRJ Fayray|MartinRJ Fayray]] 14:48, 19 October 2013 (PDT)

:::::That oddly had more to do with which template was being used. For whatever reason multilang wasn't working right and so you were getting the english version of the template (my new keyboard arrived, it's so nice to have a Z key again). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:38, 19 October 2013 (PDT)

:::One more thing, can you please point me to the "specifiers does not support negative indexes." template - it's being used here: https://wiki.secondlife.com/wiki/LlJsonSetValue/de - Thanks! --[[User:MartinRJ Fayray|MartinRJ Fayray]] 14:36, 20 October 2013 (PDT)
:::Yet another thing: How do I translate the template that shows a 'Contents' nav-box at the top right of each page, e.g. https://wiki.secondlife.com/wiki/JSON_APPEND/de - it should be translated from "Contents" to "Inhalt". Thank you much! PS: found out how to use the multilang template. --[[User:MartinRJ Fayray|MartinRJ Fayray]] 18:19, 20 October 2013 (PDT)
:::I'm done with the translation of LSL_JSON so far, if you find any errors, please let me know. --[[User:MartinRJ Fayray|MartinRJ Fayray]] 19:48, 20 October 2013 (PDT)

::::Nothing I can do about "Contents". That is Media Wiki. Unless we write our own. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:16, 21 October 2013 (PDT)
:::I don't speak German but it all looks good. However don't use multilang directly unless you have to. There is secondary categorization that multilang does which doesn't get setup if you use it directly. The LSL templates all have it set so you don't need to do anything. And you don't need to worry multilang gets called before everything else in the lsl templates.
:::I've updated the Constant template (bug fixes). -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 23:11, 22 October 2013 (PDT)
:::P.S. I'm surprised you haven't asked me about the haiku. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 23:11, 22 October 2013 (PDT)
::::What does it?--[[User:MartinRJ Fayray|MartinRJ Fayray]] 23:18, 22 October 2013 (PDT)

User talk:Strife Onizuka

2013-10-23T06:18:34Z

MartinRJ Fayray: /* German translation of llList2Json */

Template:LSL Constants/JSON/de

2013-10-23T05:29:30Z

MartinRJ Fayray: Replaced misleading word "HTML-Cod" with just "HTML" (my guess was that Strife changed it to fit into the column)

{{Multi-lang||/de}}
{{{!}} {{prettytable}}
{{!}}- {{hl2}}
! {{!}} Typ-Bezeichner
! {{!}} Wert
! {{!}} Unicode
! {{!}} {{LSLGC|Encoding/URL{{#var:lang}}|URL-Code}}
! {{!}} HTML
! {{!}} Beschreibung
{{!}}-
{{!}} {{LSL Const/de|JSON_INVALID|string|﷐}}
{{!}} {{#var:value}}
{{!}} {{Unicode|FDDO}}
{{!}} "%EF%B7%90"
{{!}} &#xFDD0;
{{!}} Rückgabewert wenn die Daten nicht wohlgeformt sind.
{{!}}-
{{!}} {{LSL Const/de|JSON_OBJECT|string|﷑}}
{{!}} {{#var:value}}
{{!}} {{Unicode|FDD1}}
{{!}} "%EF%B7%91"
{{!}} &#xFDD1;
{{!}}
{{!}}-
{{!}} {{LSL Const/de|JSON_ARRAY|string|﷒}}
{{!}} {{#var:value}}
{{!}} {{Unicode|FDD2}}
{{!}} "%EF%B7%92"
{{!}} &#xFDD2;
{{!}}
{{!}}- {{#if:{{{subset|}}}||
{{!}}-
{{!}} {{LSL Const/de|JSON_NUMBER|string|﷓}}
{{!}} {{#var:value}}
{{!}} {{Unicode|FDD3}}
{{!}} "%EF%B7%93"
{{!}} &#xFDD3;
{{!}}
{{!}}-
{{!}} {{LSL Const/de|JSON_STRING|string|﷔}}
{{!}} {{#var:value}}
{{!}} {{Unicode|FDD4}}
{{!}} "%EF%B7%94"
{{!}} &#xFDD4;
{{!}}
{{!}}-
{{!}} {{LSL Const/de|JSON_NULL|string|﷕}}
{{!}} {{#var:value}}
{{!}} {{Unicode|FDD5}}
{{!}} "%EF%B7%95"
{{!}} &#xFDD5;
{{!}}
{{!}}-
{{!}} {{LSL Const/de|JSON_TRUE|string|﷖}}
{{!}} {{#var:value}}
{{!}} {{Unicode|FDD6}}
{{!}} "%EF%B7%96"
{{!}} &#xFDD6;
{{!}}
{{!}}-
{{!}} {{LSL Const/de|JSON_FALSE|string|﷗}}
{{!}} {{#var:value}}
{{!}} {{Unicode|FDD7}}
{{!}} "%EF%B7%97"
{{!}} &#xFDD7;
{{!}}
{{!}}-
{{!}} {{LSL Const/de|JSON_DELETE|string|﷘}}
{{!}} {{#var:value}}
{{!}} {{Unicode|FDD8}}
{{!}} "%EF%B7%98"
{{!}} &#xFDD8;
{{!}} Wird zusammen mit [[llJsonSetValue{{#var:lang}}|llJsonSetValue]] benutzt, um ein Schlüssel-Wert-Paar zu löschen.
{{!}}-
}}{{!}}-
{{!}}}<noinclude>
{{{{PAGENAMEE}}|}}
{{{{PAGENAMEE}}|subset=*}}
</noinclude>

LlJsonSetValue/de

2013-10-22T05:45:34Z

MartinRJ Fayray: Replaced LSL_Function/negative index/de with LSL_Function/negative index{{#var:lang}}

{{Multi-lang||/de}}
{{LSL Function{{#var:lang}}
|inject-2={{Issues/BUG-3692}}
|inject-3={{LSL_Function/negative index{{#var:lang}}|false|specifiers|nc=*}}
|func_id=|func_sleep=0.0|func_energy=10.0
|func=llJsonSetValue
|return_type=string
|p1_type=string|p1_name=Json|p1_desc=Ausgangsdaten (JSON)
|p2_type=list|p2_name=Spezifizierer|p2_desc=Position an der ein Wert hinzugefügt, geändert oder gelöscht werden soll.
|p3_type=string|p3_name=Wert|p3_desc=Der neue Wert oder [[JSON_DELETE{{#var:lang}}|JSON_DELETE]].|p3_hover=Der neue Wert oder JSON_DELETE.
|func_footnote
|func_desc=Bei Erfolg gibt diese Funktion einen neuen [http://json.org JSON] - ''String'' zurück, bestehend aus {{LSLPT|Json}} mit dem neuen {{LSLPT|Wert}} (an der Stelle überschrieben) der in {{LSLPT|Spezifizierer}} definiert wurde.

Wenn der Funktionsaufruf fehlschlägt (typischerweise weil ein ungültiger Array-Index außerhalb des gültigen Bereichs spezifiziert wurde) wird [[JSON_INVALID{{#var:lang}}|JSON_INVALID]] zurückgegeben.

Ein "ungültiger Array-Index außerhalb des gültigen Bereichs" (out of range array index) bedeutet, dass einer der Integer-{{LSLPT|Spezifizierer}} größer ist als die Länge des vorhandenen Arrays auf der entsprechenden Ebene mit dem Json Text, oder größer als 0 auf einer Ebene auf der kein Array existiert.

Der spezielle [[JSON_APPEND{{#var:lang}}|JSON_APPEND]] - {{LSLPT|Spezifizierer}} wird ebenfalls akzeptiert. Er fügt den {{LSLPT|Wert}} an das Ende des Arrays in der entsprechenden Ebene (definiert durch {{LSLPT|Spezifizierer}}) an. Vorsicht ist geboten, wenn diese Ebene kein Array ist, da der existierende Wert dann überschrieben wird und mit einem Array ersetzt wird, welches dann den {{LSLPT|Wert}} an der ersten Index - Stelle (0) enthält.

Im Gegensatz zu [[Liste{{#var:lang}}|Listen]] und [[String{{#var:lang}}|Strings]] werden negative Indexe in Json-Arrays '''nicht''' unterstützt.

Wenn ein existierender "Key" dem {{LSLPT|Spezifizierer}} auf der entsprechenden Ebene entspricht, wird dessen Wert mit dem neuen {{LSLPT|Wert}} überschrieben (außer wenn {{LSLPT|Wert}} der besondere [[JSON_DELETE{{#var:lang}}|JSON_DELETE]] Parameter ist).

Existiert an dieser - durch {{LSLPT|Spezifizierer}} definierten - Stelle kein Wert, wird ein neues Schlüssel-Wert-Paar innerhalb des Json-Objekts erzeugt.

Um einen existiertenden Wert an der durch {{LSLPT|Spezifizierer}} definierten Stelle zu löschen, verwenden Sie als {{LSLPT|Wert}} das Schlüsselwort [[JSON_DELETE{{#var:lang}}|JSON_DELETE]]. Dieser Vorgang entfernt dabei keine leeren Objekte oder Arrays aus höheren Ebenen.

Wenn {{LSLPT|Wert}} gleich [[JSON_TRUE{{#var:lang}}|JSON_TRUE]], [[JSON_FALSE{{#var:lang}}|JSON_FALSE]] oder [[JSON_NULL{{#var:lang}}|JSON_NULL]] ist, wird der Wert entsprechend an der durch {{LSLPT|Spezifizierer}} definierten Stelle als Text 'true', 'false' oder 'null' innerhalb von {{LSLPT|Json}} gesetzt.
|return_text=
|spec=Siehe auch [[Json_usage_in_LSL{{#var:lang}}|Verwendung von JSON in LSL]]
|constants
|examples=
<lsl>
string TEST_STRING_JSON;

init()
{
TEST_STRING_JSON = "[9,\"<1,1,1>\",false,{\"A\":8,\"Z\":9}]";

// [9,"<1,1,1>",false,{"A":8,"Z":9}]
say("Original TEST_STRING_JSON: " + TEST_STRING_JSON);
}

run_json_test(string input)
{
string output;

// changing values within the json string

// change the first value in the array to 10
output = llJsonSetValue(input, [0], "10");

// [10,"<1,1,1>",false,{"A":8,"Z":9}]
say("( 1): " + output);

// change the third value in the array to 'true'
output = llJsonSetValue(input, [2], JSON_TRUE);

// [9,"<1,1,1>",true,{"A":8,"Z":9}]
say("( 2): " + output);

// change the value of "A" within the Json object to 3
output = llJsonSetValue(input, [3, "A"], "3");

// [9,"<1,1,1>",false,{"A":3,"Z":9}]
say("( 3): " + output);

// adding a value or new key-value-pair within the input

// add the value "Hello" to the end of the array
// NOTE: One cannot insert, only add to the end
output = llJsonSetValue(input, [JSON_APPEND], "Hello");

// [9,"<1,1,1>",false,{"A":8,"Z":9},"Hello"]
say("( 4): " + output);

// add the key-value-pair "B":10 to the object
output = llJsonSetValue(input, [3, "B"], "10");

// [9,"<1,1,1>",false,{"A":8,"B":10,"Z":9}]
say("( 5): " + output);

// Things to look out for when modifying Json text
// ~!~ Be careful when using this function ~!~

// out of bounds array assignment:
// defined as attempting to add a value to a position ...
// ...greater than the length of the array (which may be 0)
// JSON_APPEND is ALWAYS the preferred way to add to an array
output = llJsonSetValue(input, [5], "10");

// %EF%B7%90 (URL escaped JSON_INVALID)
say("( 6): " + llEscapeURL(output));

// BUT, this works, since it is in bounds
// (eqivalent to JSON_APPEND in this case)
output = llJsonSetValue(input, [4], "10");

// [9,"<1,1,1>",false,{"A":8,"Z":9},10]
say("( 7): " + output);

// careless formation of new arrays
// ( the 4 and all subsequent 0's are all in bounds.)
output = llJsonSetValue(input, [4, 0, 0, 0], "10");

// [9,"<1,1,1>",false,{"A":8,"Z":9},[[[10]]]]
say("( 8): " + output);

// overwriting an object with an array:
// ~!~ mistaken use of JSON_APPEND on an object ~!~
output = llJsonSetValue(input, [3, JSON_APPEND], "10");

// [9,"<1,1,1>",false,[10]]
say("( 9): " + output);

// careless formation of new objects
// NOTE: "Key" assignemts will NEVER result in a return of JSON_INVALID!
output = llJsonSetValue(input, [3, "W", "X"], "10");

// [9,"<1,1,1>",false,{"A":8,"W":{"X":10},"Z":9}]
say("(10): " + output);

output = llJsonSetValue(input, [3, "W", "X", "Y"], "10");

// [9,"<1,1,1>",false,{"A":8,"W":{"X":{"Y":10}},"Z":9}]
say("(11): " + output);

// overwriting an array with an object
output = llJsonSetValue(input, ["X"], "10");

// {"X":10}
say("(12): " + output);

// special case considerations:

// BUG-3692: (NOTE: Corrected in release 13.09.21.281328!)
// a bug where, instead of JSON_INVALID being returned, if the out of
// bounds index is at a lower level than the topmost (root) level, a
// non-compliant JSON text would be formed
output = llJsonSetValue(input, [1, 7], "Disappearing Text");

// Note the "empty" second position that resulted in the returned array
// [9,,false,{"A":8,"Z":9}]
// (But now correctly shows JSON_INVALID)
say("(13): " + output);

// though there is no way to directly delete a key-value-pair
// nor remove a value from an array,
// the use of JSON_NULL may prove adequate
output = llJsonSetValue(input, [3, "A"], JSON_NULL);

// [9,"<1,1,1>",false,{"A":null,"Z":9}]
say("(14): " + output);

// if a JSON text object has been formed with llList2Json()
// that contains one or more duplicated "Keys", (allowable
// but NOT recommended!) ANY change
// made to that object will correct the condition,
// with all but the last such "Key" being removed
output = llList2Json(JSON_OBJECT, ["A", 1, "A", 2, "A", 3, "B", 4, "B", 4]);

// both Keys "A" and "B" are duplicated
// {"A":1,"A":2,"A":3,"B":4,"B":4}
say("(15): " + output);

// only the last value of the duplications is accessable though

// 3
say("(16): " + llJsonGetValue(output, ["A"]));

// condition corrected by adding a key-value-pair...

// {"A":3,"B":4,"Z":5}
say("(17): " + llJsonSetValue(output, ["Z"], "5"));

// ... or by changing a value

// {"A":5,"B":4}
say("(18): " + llJsonSetValue(output, ["A"], "5"));
}

say(string message)
{
llOwnerSay(message);
// llRegionSayTo(llGetOwner(), PUBLIC_CHANNEL, message);
// llWhisper(PUBLIC_CHANNEL, message);
}

default
{
on_rez(integer start_param)
{
llResetScript();
}

state_entry()
{
init();
}

touch_end(integer num_detected)
{
// copy 'TEST_STRING_JSON' from the following function call
// to the string 'input' in the function declaration
// and run a test on 'input' to not (!) modify 'TEST_STRING_JSON'
// but its copy instead
run_json_test(TEST_STRING_JSON);
}
}
</lsl>
|caveats=
|helpers
|also_functions={{LSL DefineRow||[[llList2Json{{#var:lang}}|llList2Json]]|}}
{{LSL DefineRow||[[llJson2List{{#var:lang}}|llJson2List]]|}}
{{LSL DefineRow||[[llJsonGetValue{{#var:lang}}|llJsonGetValue]]|}}
{{LSL DefineRow||[[llJsonValueType{{#var:lang}}|llJsonValueType]]|}}
|also_events
|also_tests
|also_articles={{LSL DefineRow||[[Typecast{{#var:lang}}|Typecast]]|}}
|notes=
|permission
|negative_index
|sort=JsonSetValue
|cat1=List
|cat2=String
|cat3=Data Conversion
|cat4=JSON
|history = Veröffentlichungsdatum [[ Release_Notes/Second_Life_Server/13#13.05.20.276191 | 20/05/2013 ]]
}}

LSL Portal/de

2013-10-21T02:57:20Z

MartinRJ Fayray: /* {{LSLGC||LSL Kategorien}} added LSL_JSON/de */

{{Multi-lang}}

{{LSL Header/de}}

<div id="box" style="background: red; -moz-border-radius: 10px; text-align: center; border: 1px solid black; padding: 2px">

{|width="100%" style="background: #f9f9f9; -moz-border-radius: 8px; text-align: center; border: 1px solid black;"
|width="50px" valign="center" align="center"|[[Image:Wrench.png]]
|Dieses Portal befindet sich derzeit in Bearbeitung. Wirf einen Blick auf die [[{{TALKPAGENAME}}|zugehörige Diskussionsseite]], falls Du dabei helfen möchtest.
|}

</div>__NOTOC__
== Willkommen im Second Life LSL Portal! ==
Dies ist eine gemeinschaftliche Bestrebung eine genaue Beschreibung der Scriptsprache von {{LL|SL}} zu liefern: {{HoverText|LSL|Linden Scripting Language}}. 
Es ist als offene Dokumentation gedacht, die Scriptern aller Erfahrungsstufen helfen soll. Fühle Dich dazu eingeladen zur hierzu beizutragen, Artikel zu editieren oder neu anzulegen. Siehe ebenfalls: [[How to choose a wiki]]{{nnlink/de}}.

Du willst die Linden Scripting Language (LSL) erlernen? Teste eines der [[LSL Tutorial|LSL Tutorien]]{{nnlink/de}}.

Bitte kopiere keine Informationen aus anderen Quellen hier hinein, wenn du dir nicht absolut sicher bist über evtl. Copyrightverletzungen.
Wirf einen Blick auf [[Talk:LSL Portal]]{{nnlink/de}} für weitere Informationen.

<div id="box" style="background: #f9f9f9; -moz-border-radius: 10px; text-align: center; border: 1px solid black; padding: 2px">
Verweise auf englischsprachige Seiten sind mit {{nnlink/de}} markiert. 
Bitte beachtet, dass deutschsprachige Seiten ggf. nicht aktuell sind.
</div>
----

<div id="box">
{| width="100%" rules="all" style="border-width: 0px; border-spacing: 5px;"
|-valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
|height="1" width="30%"|

== LSL Portal==
<div style="padding: 0.5em">
* [[LSL Editing Primer|LSL Editing Primer]]{{nnlink/de}} - wiki editing how to
* [[LSL Portal Guidelines|Portal Guidelines]]{{nnlink/de}} - wiki editing should's
* [[LSL Portal To-do|Portal To-Do]]{{nnlink/de}} - wiki edits most needed where
* [[LSL Portal Translation Project|LSL Portal Translation Project]]{{nnlink/de}} - translation coordination

</div>
|height="1" width="30%" rowspan="2"|

== LSL Sprachreferenz ==
<div style="padding: 0.5em">
* [[:Category:LSL Constants|Konstanten]]{{nnlink/de}}
* [[:Category:LSL Events|Ereignisse]]{{nnlink/de}}
* {{LSLGC|Flow Control}}{{nnlink/de}}
*:[[for]]{{nnlink/de}}, [[if]]{{nnlink/de}}, [[while]]{{nnlink/de}}, [[do-while]]{{nnlink/de}}, [[jump]]{{nnlink/de}}, [[return]]{{nnlink/de}}, [[state]]{{nnlink/de}}
* [[:Category:LSL Functions/de|Funktionen]]
*:[{{fullurl:Category:LSL_Functions|from=}} (Seite 1: A..O)], [{{fullurl:Category:LSL_Functions|from=P}} (Seite 2: P..Z)]
* [[LSL Operators|Operatoren]]{{nnlink/de}}
* [[state|States]]{{nnlink/de}}
* [[:Category:LSL Types|Typen]]{{nnlink/de}}
*:[[integer]]{{nnlink/de}}, [[float]]{{nnlink/de}}, [[string]]{{nnlink/de}}, [[key]]{{nnlink/de}}, [[list]]{{nnlink/de}}, [[vector]]{{nnlink/de}}, [[rotation]]{{nnlink/de}}
* [[LSL Variables|Variablen]]{{nnlink/de}}

* [[LSL Errors|Fehler]]{{nnlink/de}}
</div>
|height="1" width="25%" rowspan="5"|

== {{LSLGC||LSL Kategorien}} ==
<div style="padding: 0.5em">
{| border="0" cellspacing="0" cellpadding="0"
|-valign="top"
|width="50%"|
* [[:Category:LSL Alpha|Alpha]]{{nnlink/de}}
* [[:Category:LSL Animation|Animation]]{{nnlink/de}}
* [[:Category:LSL Attachment|Attachments]]{{nnlink/de}}
* [[:Category:LSL Avatar|Avatar]]{{nnlink/de}}
* [[:Category:LSL Camera|Kamera]]{{nnlink/de}}
* [[:Category:LSL Collision|Kollision]]{{nnlink/de}}
* [[:Category:LSL Color|Farbe]]{{nnlink/de}}
* [[:Category:LSL Controls|Steuerung]]{{nnlink/de}}
* [[:Category:LSL Communications|Kommunikation]]{{nnlink/de}}
* [[:Category:LSL Face|Fläche(Face)]]{{nnlink/de}}
* [[:Category:LSL Group|Gruppen]]{{nnlink/de}}
* [[:Category:LSL Inventory|Inventar]]{{nnlink/de}}
* [[:Category:LSL JSON/de|JSON]]
* [[:Category:LSL Light|Licht]]{{nnlink/de}}
* [[:Category:LSL Link|Link]]{{nnlink/de}}
* [[:Category:LSL Math|Mathematik]]{{nnlink/de}}
* [[:Category:LSL Needs Example|Benötigt Beispiel]]{{nnlink/de}}
* [[:Category:LSL Permissions|Berechtigungen]]{{nnlink/de}}
* [[:Category:LSL Physics|Physik]]{{nnlink/de}}
* [[:Category:LSL Prim|Primitive]]{{nnlink/de}}
* [[:Category:LSL Rotation|Rotation]]{{nnlink/de}}
* [[:Category:LSL Sensor|Sensor]]{{nnlink/de}}
* [[:Category:LSL Sound|Sound]]{{nnlink/de}}
* [[:Category:LSL Texture|Textur]]{{nnlink/de}}
* [[:Category:LSL Time|Zeit]]{{nnlink/de}}
* [[:Category:LSL Video|Video]]{{nnlink/de}}
* [[:Category:LSL Vehicle|Fahrzeuge]]{{nnlink/de}}
* [[:Category:LSL World|Welt]]{{nnlink/de}}
|width="50%"|
* {{LSLGC|Avatar}}{{nnlink/de}}
** {{LSLGC|Animation}}{{nnlink/de}}
** {{LSLGC|Attachment}}{{nnlink/de}}
** {{LSLGC|Camera|Kamera}}{{nnlink/de}}
** {{LSLGC|Controls|Steuerung}}{{nnlink/de}}
** {{LSLGC|Sit|Sitzen}}{{nnlink/de}}
* {{LSLGC|Communications|Kommunikation}}{{nnlink/de}}
** {{LSLGC|Chat}}{{nnlink/de}}
** {{LSLGC|HTTP}}{{nnlink/de}}
** {{LSLGC|XML-RPC}}{{nnlink/de}}
* [[:Category:LSL Detected|Detection]]{{nnlink/de}}
** {{LSLGC|Collision|Kollision}}{{nnlink/de}}
** {{LSLGC|Touch}}{{nnlink/de}}
** {{LSLGC|Sensor}}{{nnlink/de}}
* {{LSLGC|Functions|Funktionen}}{{nnlink/de}}
** {{LSLGC|God Mode|Gott Modus}}{{nnlink/de}}
* {{LSLGC|Inventory|Inventar}}{{nnlink/de}}
** {{LSLGC|Creator|Urheber}}{{nnlink/de}}
** {{LSLGC|Notecard}}{{nnlink/de}}
** {{LSLGC|Owner|Besitzer}}{{nnlink/de}}
* {{LSLGC|Media|Medien}}{{nnlink/de}}
** {{LSLGC|Sound}}{{nnlink/de}}
** {{LSLGC|Video}}{{nnlink/de}}
* {{LSLGC|Movement|Bewegung}}{{nnlink/de}}
** {{LSLGC|Physics|Physik}}{{nnlink/de}}
*** {{LSLGC|Damping|Dämpfung}}{{nnlink/de}}
*** {{LSLGC|Hover|Schweben}}{{nnlink/de}}
** {{LSLGC|Rotation}}{{nnlink/de}}
* {{LSLGC|Object|Objekt}}{{nnlink/de}}
** {{LSLGC|Link}}{{nnlink/de}}
** {{LSLGC|Vehicle|Fahrzeug}}{{nnlink/de}}
* {{LSLGC|Permissions|Berechtigungen}}{{nnlink/de}}
** [[:Category:LSL Permissions/Asset|Asset]]{{nnlink/de}}
** [[:Category:LSL Permissions/Script|Script]]{{nnlink/de}}
* {{LSLGC|Prim|Primitive}}{{nnlink/de}}
** {{LSLGC|Effects|Effekte}}{{nnlink/de}}
*** {{LSLGC|Particles|Partikel}}{{nnlink/de}}
*** {{LSLGC|Light|Licht}}{{nnlink/de}}
** {{LSLGC|Face|Fläche(Face)}}{{nnlink/de}}
*** {{LSLGC|Alpha|Transparenz}}{{nnlink/de}}
*** {{LSLGC|Color|Farbe}}{{nnlink/de}}
*** {{LSLGC|Texture|Textur}}{{nnlink/de}}
* {{LSLGC|Script}}{{nnlink/de}}
** {{LSLGC|Error|Fehler}}{{nnlink/de}}
*** [[:Category:LSL Error/Math|Mathematische Fehler]]{{nnlink/de}}
** {{LSLGC|Keywords|Schlüsselwörter}}{{nnlink/de}}
** {{LSLGC|Math|Mathematisches}}{{nnlink/de}}
* {{LSLGC|Region}}{{nnlink/de}}
** {{LSLGC|Ground|Boden}}{{nnlink/de}}
** {{LSLGC|Parcel|Parzelle}}{{nnlink/de}}
** {{LSLGC|Security|Sicherheit}}{{nnlink/de}}
** {{LSLGC|Time|Zeit}}{{nnlink/de}}
|}
</div>
|-valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
|height="1"|

== Entwickler Ressourcen ==
<div style="padding: 0.5em">
* [[LSL Tutorial|Tutorien]]{{nnlink/de}}
* [[:Category:LSL Teachers|LSL Lehrer]]{{nnlink/de}}
* [[:Category:LSL Mentors|LSL Mentoren]]{{nnlink/de}}
* [[:Category:LSL Examples|LSL Beispiele]]{{nnlink/de}}
* [[:Category:LSL Library|Script Sammlung]]{{nnlink/de}}
* [[LSL Protocol|Protokoll Austausch]]{{nnlink/de}}
* [[LSL Useful Function WishList|Wunschliste nützlicher Funktionen]]{{nnlink/de}}
* [[LSL Style Guide|Stilanleitung]]{{nnlink/de}}
* [[LSL Script Efficiency|Script Effizenz]]{{nnlink/de}}
* [[LSL Script Memory|Script Speicher]]{{nnlink/de}}
* [[LSL Write Once Debug Everywhere]]{{nnlink/de}}
* [[LSL_Alternate_Editors |OffWorld Editioren/Entwicklungsumgebungen]]{{nnlink/de}}
* [[LSL Test Harness | Inworld test harness]]{{nnlink/de}}
* [[LSL Benchmarking Scripts | Benchmarking Scripte]]{{nnlink/de}}
</div>
|-valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
|height="1" colspan="2"|
{{LSL News}}
|-valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
|height="1" colspan="2"|
{{LSL Bugs}}
|-valign="top" rules="all" style="border-width: 1px 1px 1px 1px; padding: 1px 1px 1px 1px; border-style: solid solid solid solid; border-color: gray;"
|colspan="2"|

== Andere LSL Wikis ==
<div style="padding: 0.5em">
* [http://www.lslwiki.net/lslwiki/ lslWiki]
* [http://rpgstats.com/wiki/ RPGStats lslWiki] (Mediawiki Mirror / Japanese Translations)
</div>

== Snapshot Mirrors ==
<div style="padding: 0.5em">
* [http://www.cheesefactory.us/lslwm LSL Wiki Mirror 07-07-2007] (downloadable)
* [http://sha.dtm-network.com/all/lslwm/ LSL Wiki Mirror 01-05-2007 Alternative]
</div>
|}
</div>

[[Category:Portals]]

[[Category:Creation]]

[[Category:LSL|*]]

Verwendung von JSON in LSL/de

2013-10-21T02:54:49Z

MartinRJ Fayray: fixed punctuation

{{Multi-lang||/de}}
{{LSL Header/de|lm=*}}{{LSLC|}}{{LSLC|JSON{{#var:lang}}|*Verwendung von JSON in LSL}}
==Übersicht==
[http://www.json.org/ JSON] (JavaScript Object Notation) ist ein Textformat (unabhängig von Programmiersprache und Architektur) um [http://de.wikipedia.org/wiki/Serialisierung Datenstrukturen zu serialisieren], ähnlich wie es [http://de.wikipedia.org/wiki/XML XML] für Dokumente macht, aber in einer wesentlich kompakteren Form.
Es wird in der einfachsten Form als ein reiner String dargestellt, der in seinem Aufbau einem [http://tools.ietf.org/html/rfc4627 Regelset] folgt.
Diese Regeln erlauben die Codierung, Manipulation, Speicherung, Übermittlung und Decodierung von komplexen Datenstrukturen in einer kurzen, lesbaren Form.
Json-Text kann man benutzen, um zwischen JSON-kompatiblen Anwendungen zu kommunizieren, und wird in erster Linie für die Webclient-Server-Kommunikation verwendet.

JSON ermöglicht es [http://de.wikipedia.org/wiki/Objekt_%28Programmierung%29 Objekte], [http://de.wikipedia.org/wiki/Datenbank Datenbanken] und komplexe und abstrakte Datentypen zu erzeugen ([http://de.wikipedia.org/wiki/Feld_%28Datentyp%29 multidimensionale und assoziative Arrays], [http://de.wikipedia.org/wiki/Last_In_%E2%80%93_First_Out Stacks], [http://de.wikipedia.org/wiki/First_In_%E2%80%93_First_Out Queues] und [http://de.wikipedia.org/wiki/Liste_%28Datenstruktur%29 Listen]).

Da LSL diese Datentypen nicht unterstützt, werden zur Anwendung dieser Datentypen user-generierte Funktionen benötigt (z.B. getAllKeys(), getArrayLength(), deleteItem(), und Iterator-Operatoren),
um von den Vorteilen (wie Datenkapselung, Speicher-Einsparung für lange Listen, Verschachtelung von vermischten Datenstrukturen) die JSON ermöglichen, profitieren zu können.

Ein LSL-basiertes Testskript für diese Funktionen kann man hier abrufen: [[Json_usage_in_LSL/TestScript]].

==Typenkonvertierung==

Siehe [[llJsonValueType{{#var:lang}}|llJsonValueType]]

==Neue LSL Funktionen==

*[[LlJson2List{{#var:lang}}|LlJson2List]]
*[[LlJsonGetValue{{#var:lang}}|LlJsonGetValue]]
*[[LlJsonSetValue{{#var:lang}}|LlJsonSetValue]]
*[[LlJsonValueType{{#var:lang}}|LlJsonValueType]]
*[[LlList2Json{{#var:lang}}|LlList2Json]]

'''''HINWEIS''''' Bitte besuchen Sie auch die originale Englische Version dieser Seite für weitere Informationen, wie Beispielskripts etc.: [[Json_usage_in_LSL]].