Menu System 2 (Second Life) - Revision history

Grigbertz: Added Category

2009-02-23T11:26:18Z

Added Category

←Older revision		Revision as of 11:26, 23 February 2009
Line 1:		Line 1:
		+	{{SL}}
	Menu System 2 is a note-card-configured system for making easily interchangeable and configurable menu trees in second Life objects.		Menu System 2 is a note-card-configured system for making easily interchangeable and configurable menu trees in second Life objects.

M: /* Handing over to another instance */

2008-11-19T19:46:43Z

Handing over to another instance

←Older revision		Revision as of 19:46, 19 November 2008
Line 354:		Line 354:
	To call another menu system, instead use a linked message:		To call another menu system, instead use a linked message:
	[button] endmenu		[button] endmenu
-	~~mesagelinkset~~ \| menu newmenu	+	messagelinkset \| menu newmenu
	Sinde we want this menu system to stop its menus, we use the button modifier "endmenu".		Sinde we want this menu system to stop its menus, we use the button modifier "endmenu".

M at 19:39, 19 November 2008

2008-11-19T19:39:58Z

←Older revision		Revision as of 19:39, 19 November 2008
Line 255:		Line 255:
	\|}		\|}

-	~~= Animation helpers =~~

	= Communication =		= Communication =

M: /* Conditional variable substitution */

2008-11-19T19:39:01Z

Conditional variable substitution

←Older revision		Revision as of 19:39, 19 November 2008
Line 110:		Line 110:
	Conditionals (see below) can also be used in menu descriptions, using this construction:		Conditionals (see below) can also be used in menu descriptions, using this construction:

-	?{condition?string if true:string if false}?	+	${condition?string if true:string if false}$

	This allows you to write things like this in descriptions		This allows you to write things like this in descriptions

M: /* Descriptions and variable substitution */

2008-11-19T19:38:17Z

Descriptions and variable substitution

←Older revision		Revision as of 19:38, 19 November 2008
Line 105:		Line 105:
	Like this:		Like this:
	* ${object}$ is owned by ${owner}$		* ${object}$ is owned by ${owner}$
		+
		+	===Conditional variable substitution===
		+
		+	Conditionals (see below) can also be used in menu descriptions, using this construction:
		+
		+	?{condition?string if true:string if false}?
		+
		+	This allows you to write things like this in descriptions
		+
		+	* Choose operator's buttons settings.
		+	* Current settings:
		+	* - ${isLocked?The button is not detachable.:The button is detachable.}$
		+	* - ${isPublic?The button's on/off-messages are public.:The button's on/off-messages are private.}$
		+	* - ${isPressSelf?The wearer can self press the button.:The wearer can not press the button.}$
		+
		+	Note the different strings for true and false conditions.

	=== Button definitions ===		=== Button definitions ===

M: /* Special role conditions */

2008-11-19T19:28:50Z

Special role conditions

←Older revision		Revision as of 19:28, 19 November 2008
Line 151:		Line 151:

	The following conditions can be used in expressions above, even if they have not been sent to the menu system through linked messages. They are instead derived from the menu user's role(s).		The following conditions can be used in expressions above, even if they have not been sent to the menu system through linked messages. They are instead derived from the menu user's role(s).
-	* ~~isprivileged~~	+	* isPrivileged
-	* ~~isoperator~~	+	* isOperator
-	* ~~isowner~~	+	* isOwner
-	* ~~isother~~	+	* isOther

	For example, the below button pair is only available if the current user is an operator:		For example, the below button pair is only available if the current user is an operator:
-	[~~lock~~] ifallof ~~isoperator unlocked~~	+	[Lock] ifallof isOperator !isLocked
-	messagelinkset \| lock	+	messagelinkset \| lock
-	[~~unlock~~] ifallof ~~isoperator locked~~	+	[Unlock] ifallof isOperator isLocked
-	messagelinkset \| unlock	+	messagelinkset \| unlock

	=== Hide Inactive Modifier ===		=== Hide Inactive Modifier ===

M: /* Button Condition Expression Modifier */

2008-11-19T19:26:46Z

Button Condition Expression Modifier

←Older revision		Revision as of 19:26, 19 November 2008
Line 138:		Line 138:
	If any more complex logical combination is needed than those above, the state-maintaining script better define that combination as a single		If any more complex logical combination is needed than those above, the state-maintaining script better define that combination as a single
	new condition and send that one.		new condition and send that one.
		+
		+	=== Negating a Condition ===
		+
		+	A condition can be negated by preceding it with a "!". This is useful when writing toggle buttons. For example:
		+
		+	[Free] if isLocked
		+	messagelinkedset \| setLockOn
		+	[Lock] if !isLocked
		+	messagelinkedset \| setLockOff

	=== Special role conditions ===		=== Special role conditions ===

M: /* Linked Messages Listened to */

2008-10-19T12:02:29Z

Linked Messages Listened to

←Older revision		Revision as of 12:02, 19 October 2008
Line 305:		Line 305:
	\|		\|
	\| Revokes all operator roles.		\| Revokes all operator roles.
-	\| llMessageLinked(LINK_THIS, 0, "deleteOperators", NULL_KEY);<	+	\| llMessageLinked(LINK_THIS, 0, "deleteOperators", NULL_KEY);
		+	\|-
		+	\| setPrivileged
		+	\| givenname familyname
		+	\| Gives the named avatar the privileged role.
		+	\| llMessageLinked(LINK_THIS, 0, "setPrivileged" + name, NULL_KEY);<br>llMessageLinked(LINK_THIS, 0, "setPrivilegedTuft Meili", NULL_KEY);
		+	\|-
		+	\| removePrivileged
		+	\|
		+	\| Revokes the privileged role from the avatar currently having it.
		+	\| llMessageLinked(LINK_THIS, 0, "removePrivileged", NULL_KEY);
	\|}		\|}

M: /* Special role conditions */

2008-10-19T11:55:32Z

Special role conditions

←Older revision		Revision as of 11:55, 19 October 2008
Line 146:		Line 146:
	* isowner		* isowner
	* isother		* isother
		+
		+	For example, the below button pair is only available if the current user is an operator:
		+	[lock] ifallof isoperator unlocked
		+	messagelinkset \| lock
		+	[unlock] ifallof isoperator locked
		+	messagelinkset \| unlock

	=== Hide Inactive Modifier ===		=== Hide Inactive Modifier ===

M: /* Roles */

2008-10-19T11:52:08Z

Roles

←Older revision		Revision as of 11:52, 19 October 2008
Line 1:		Line 1:
	Menu System 2 is a note-card-configured system for making easily interchangeable and configurable menu trees in second Life objects.		Menu System 2 is a note-card-configured system for making easily interchangeable and configurable menu trees in second Life objects.

-	=Roles=	+	==Roles==

	The avatars that use the menu system can have one or more of the following roles in the menu system:		The avatars that use the menu system can have one or more of the following roles in the menu system:
Line 13:		Line 13:
	The roles of various avatars are based on linked messages sent to the menu system by other scripts in the object.		The roles of various avatars are based on linked messages sent to the menu system by other scripts in the object.

-	==Privileged==	+	===Privileged===

	Only a single user can be '''privileged'''. That user has done something to earn her special rights, such as being the owner of the single key to an object.		Only a single user can be '''privileged'''. That user has done something to earn her special rights, such as being the owner of the single key to an object.

-	==Operator==	+	===Operator===
-	'''~~Operators~~''' ~~are those~~ that has more than normal rights to operate an object, such as being the only ones that can change its configurations.	+	'''Operator''' is anyone that has more than normal rights to operate an object, such as being the only ones that can change its configurations. Normally, a list of operators is configured in a separate note card.

-	==Owner==	+	===Owner===
	'''Owner''' is the SL owner of the object in question.		'''Owner''' is the SL owner of the object in question.

-	==Other==	+	===Other===
	'''Other''' is anyone that has none of the other roles above.		'''Other''' is anyone that has none of the other roles above.
-

	=Note Card Format=		=Note Card Format=