Target References - Revision history

Rob: /* Topics */

2008-12-07T23:59:25Z

Topics

← Older revision		Revision as of 23:59, 7 December 2008
Line 30:		Line 30:
	The topics below delineate the various target references that are available within each context.		The topics below delineate the various target references that are available within each context.

	*[[~~Container Target References\|~~Container Context#references]]		*[[Container Context#references\|Container Target References]]
	*[[~~Hero Target References\|~~Hero Context#references]]		*[[Hero Context#references\|Hero Target References]]
	*[[~~Pick Target References\|~~Pick Context#references]]		*[[Pick Context#references\|Pick Target References]]
	*[[~~Thing Target References\|~~Thing Context#references]]		*[[Thing Context#references\|Thing Target References]]
	*[[~~Field Target References\|~~Field Context#references]]		*[[Field Context#references\|Field Target References]]
	*[[~~Pool Target References\|~~Pool Context#references]]		*[[Pool Context#references\|Pool Target References]]
	*[[~~Scene Target References\|~~Scene Context#references]]		*[[Scene Context#references\|Scene Target References]]
	*[[~~Layout Target References\|~~Layout Context#references]]		*[[Layout Context#references\|Layout Target References]]
	*[[~~Template Target References\|~~Template Context#references]]		*[[Template Context#references\|Template Target References]]
	*[[~~Portal Target References\|~~Portal Context#references]]		*[[Portal Context#references\|Portal Target References]]
	*[[~~Value Target References\|~~Value Context#references]]		*[[Value Context#references\|Value Target References]]
	*[[~~Table Target References\|~~Table Context#references]]		*[[Table Context#references\|Table Target References]]
	*[[~~State Target References\|~~State Context#references]]		*[[State Context#references\|State Target References]]

Rob: /* Topics */

2008-12-07T23:57:59Z

Topics

← Older revision		Revision as of 23:57, 7 December 2008
Line 30:		Line 30:
	The topics below delineate the various target references that are available within each context.		The topics below delineate the various target references that are available within each context.

	*~~{{fl\|~~Container Target References}}		*[[Container Target References\|Container Context#references]]
	*~~{{fl\|~~Hero Target References}}		*[[Hero Target References\|Hero Context#references]]
	*~~{{fl\|~~Pick Target References}}		*[[Pick Target References\|Pick Context#references]]
	*~~{{fl\|~~Thing Target References}}		*[[Thing Target References\|Thing Context#references]]
	*~~{{fl\|~~Field Target References}}		*[[Field Target References\|Field Context#references]]
	*~~{{fl\|~~Pool Target References}}		*[[Pool Target References\|Pool Context#references]]
	*~~{{fl\|~~Scene Target References}}		*[[Scene Target References\|Scene Context#references]]
	*~~{{fl\|~~Layout Target References}}		*[[Layout Target References\|Layout Context#references]]
	*~~{{fl\|~~Template Target References}}		*[[Template Target References\|Template Context#references]]
	*~~{{fl\|~~Portal Target References}}		*[[Portal Target References\|Portal Context#references]]
	*~~{{fl\|~~Value Target References}}		*[[Value Target References\|Value Context#references]]
	*~~{{fl\|~~Table Target References}}		*[[Table Target References\|Table Context#references]]
	*~~{{fl\|~~State Target References}}		*[[State Target References\|State Context#references]]

Rob at 03:58, 6 December 2008

2008-12-06T03:58:52Z

← Older revision		Revision as of 03:58, 6 December 2008
Line 25:		Line 25:
	\|-		\|-
	\|}		\|}

	~~==Use of Identity==~~

	There are a number of target references across different contexts that make use of identity tags. For each of these target references, a tag group is specified, but no actual tag. This is because the script itself implicitly identifies the tag id based on the initial context of the script. The source of the identity tag is dictated by the pick or thing that begins as the initial context, with the unique id of that object being used as the identity tag id. The group in which to locate that identity tag is specified with the target reference. If the resulting identity tag does not exist, a run-time error is reported.

	The use of identity target references has an important limitation. The identity source is based on the initial script context, and only things and picks possess identity tags. Consequently, identity target references can only be used from within scripts whose initial context is either a thing or a pick. Use from any other script results in a compilation error.

	==Topics==		==Topics==

Rob: /* Target Reference Behaviors */

2008-12-06T03:23:57Z

Target Reference Behaviors

← Older revision		Revision as of 03:23, 6 December 2008
Line 21:		Line 21:
	\|This target reference utilizes a numeric value, either returning a number or expecting to be assigned a number.		\|This target reference utilizes a numeric value, either returning a number or expecting to be assigned a number.
	\|-		\|-
	\|~~Text~~		\|String
	\|This target reference utilizes a text string, either returning a string or expecting to be assigned a string.		\|This target reference utilizes a text string, either returning a string or expecting to be assigned a string.
	\|-		\|-

Rob: /* Target Reference Behaviors */

2008-12-06T03:22:28Z

Target Reference Behaviors

← Older revision		Revision as of 03:22, 6 December 2008
Line 9:		Line 9:
	==Target Reference Behaviors==		==Target Reference Behaviors==

	Every target reference is assigned a ~~behavior~~ that ~~dictates~~ how it can be used within scripts. ~~There are three~~ different behaviors ~~that~~ are described in the table below.		Every target reference is assigned a set of behaviors that dictate how it can be used within scripts. The different behaviors are described in the table below.

	:{\| class="infotable"		:{\| class="infotable"
	\|class="leftnormal"\|Right~~-Only~~		\|class="leftnormal"\|Right
	\|This target reference can ~~only~~ be utilized on the right side of an assignment statement or with the "perform" statement. The value returned is specified within its description.		\|This target reference can be utilized on the right side of an assignment statement or with the "perform" statement. The value returned is specified within its description.
	\|-		\|-
	\|Left~~-Only~~		\|Left
	\|This target reference can ~~only~~ be utilized on the left side of an assignment statement. It must be assigned a value in accordance with its description.		\|This target reference can be utilized on the left side of an assignment statement. It must be assigned a value in accordance with its description.
	\|-		\|-
	\|~~Left-Right~~		\|Number
	\|This target reference ~~may be used on~~ either ~~the left or right side of an assignment statement,~~ or ~~it may~~ be ~~used within~~ a ~~"perform" statement~~. ~~If used on the right side~~, ~~the value returned is specified within its description. If used on the left side, it must~~ be assigned a ~~value in accordance with its description~~.		\|This target reference utilizes a numeric value, either returning a number or expecting to be assigned a number.
			\|-
			\|Text
			\|This target reference utilizes a text string, either returning a string or expecting to be assigned a string.
	\|-		\|-
	\|}		\|}

Rob at 02:39, 6 December 2008

2008-12-06T02:39:58Z

← Older revision		Revision as of 02:39, 6 December 2008
Line 6:		Line 6:

	{{note}}If the current script context is invalid, any target reference used within that context. If this occurs during run-time, the operation will be ignored and the target identifier will return zero. A suitable error will generally be displayed, but not always. An example of an invalid context is when a pick attempts to transition to a field that does not exist within that pick.		{{note}}If the current script context is invalid, any target reference used within that context. If this occurs during run-time, the operation will be ignored and the target identifier will return zero. A suitable error will generally be displayed, but not always. An example of an invalid context is when a pick attempts to transition to a field that does not exist within that pick.

			==Target Reference Behaviors==

			Every target reference is assigned a behavior that dictates how it can be used within scripts. There are three different behaviors that are described in the table below.

			:{\| class="infotable"
			\|class="leftnormal"\|Right-Only
			\|This target reference can only be utilized on the right side of an assignment statement or with the "perform" statement. The value returned is specified within its description.
			\|-
			\|Left-Only
			\|This target reference can only be utilized on the left side of an assignment statement. It must be assigned a value in accordance with its description.
			\|-
			\|Left-Right
			\|This target reference may be used on either the left or right side of an assignment statement, or it may be used within a "perform" statement. If used on the right side, the value returned is specified within its description. If used on the left side, it must be assigned a value in accordance with its description.
			\|-
			\|}

	==Use of Identity==		==Use of Identity==

Rob at 23:01, 5 December 2008

2008-12-05T23:01:36Z

← Older revision		Revision as of 23:01, 5 December 2008
Line 6:		Line 6:

	{{note}}If the current script context is invalid, any target reference used within that context. If this occurs during run-time, the operation will be ignored and the target identifier will return zero. A suitable error will generally be displayed, but not always. An example of an invalid context is when a pick attempts to transition to a field that does not exist within that pick.		{{note}}If the current script context is invalid, any target reference used within that context. If this occurs during run-time, the operation will be ignored and the target identifier will return zero. A suitable error will generally be displayed, but not always. An example of an invalid context is when a pick attempts to transition to a field that does not exist within that pick.

			==Use of Identity==

			There are a number of target references across different contexts that make use of identity tags. For each of these target references, a tag group is specified, but no actual tag. This is because the script itself implicitly identifies the tag id based on the initial context of the script. The source of the identity tag is dictated by the pick or thing that begins as the initial context, with the unique id of that object being used as the identity tag id. The group in which to locate that identity tag is specified with the target reference. If the resulting identity tag does not exist, a run-time error is reported.

			The use of identity target references has an important limitation. The identity source is based on the initial script context, and only things and picks possess identity tags. Consequently, identity target references can only be used from within scripts whose initial context is either a thing or a pick. Use from any other script results in a compilation error.

	==Topics==		==Topics==

Rob at 10:11, 5 December 2008

2008-12-05T10:11:13Z

@@ Line 3: / Line 3: @@
 ==Overview==
-When managing data via scripts, the first step is to establish the correct script context. Once you've identified the desired context, you'll then need to specify the appropriate target reference to retrieve or manipulate the specific information you want. Every script context has an assortment of target references that provide access to data pertaining to that context. The sections below delineate the various target references that are available within each context.
+When managing data via scripts, the first step is to establish the correct script context. Once you've identified the desired context, you'll then need to specify the appropriate target reference to retrieve or manipulate the specific information you want. Every script context has an assortment of target references that provide access to data pertaining to that context.
 {{note}}If the current script context is invalid, any target reference used within that context. If this occurs during run-time, the operation will be ignored and the target identifier will return zero. A suitable error will generally be displayed, but not always. An example of an invalid context is when a pick attempts to transition to a field that does not exist within that pick.

Rob: New page: {{context|Kit Reference}} ==Overview== When managing data via scripts, the first step is to establish the correct script context. Once you've identified the desired context, you'll then ...

2008-12-05T10:07:24Z

New page: {{context|Kit Reference}} ==Overview== When managing data via scripts, the first step is to establish the correct script context. Once you've identified the desired context, you'll then ...

New page

{{context|Kit Reference}}

==Overview==

When managing data via scripts, the first step is to establish the correct script context. Once you've identified the desired context, you'll then need to specify the appropriate target reference to retrieve or manipulate the specific information you want. Every script context has an assortment of target references that provide access to data pertaining to that context. The sections below delineate the various target references that are available within each context.

{{note}}If the current script context is invalid, any target reference used within that context. If this occurs during run-time, the operation will be ignored and the target identifier will return zero. A suitable error will generally be displayed, but not always. An example of an invalid context is when a pick attempts to transition to a field that does not exist within that pick.

← Older revision		Revision as of 23:59, 7 December 2008
Line 30:		Line 30:
	The topics below delineate the various target references that are available within each context.		The topics below delineate the various target references that are available within each context.

	*[[~~Container Target References\|~~Container Context#references]]		*[[Container Context#references\|Container Target References]]
	*[[~~Hero Target References\|~~Hero Context#references]]		*[[Hero Context#references\|Hero Target References]]
	*[[~~Pick Target References\|~~Pick Context#references]]		*[[Pick Context#references\|Pick Target References]]
	*[[~~Thing Target References\|~~Thing Context#references]]		*[[Thing Context#references\|Thing Target References]]
	*[[~~Field Target References\|~~Field Context#references]]		*[[Field Context#references\|Field Target References]]
	*[[~~Pool Target References\|~~Pool Context#references]]		*[[Pool Context#references\|Pool Target References]]
	*[[~~Scene Target References\|~~Scene Context#references]]		*[[Scene Context#references\|Scene Target References]]
	*[[~~Layout Target References\|~~Layout Context#references]]		*[[Layout Context#references\|Layout Target References]]
	*[[~~Template Target References\|~~Template Context#references]]		*[[Template Context#references\|Template Target References]]
	*[[~~Portal Target References\|~~Portal Context#references]]		*[[Portal Context#references\|Portal Target References]]
	*[[~~Value Target References\|~~Value Context#references]]		*[[Value Context#references\|Value Target References]]
	*[[~~Table Target References\|~~Table Context#references]]		*[[Table Context#references\|Table Target References]]
	*[[~~State Target References\|~~State Context#references]]		*[[State Context#references\|State Target References]]

← Older revision		Revision as of 23:57, 7 December 2008
Line 30:		Line 30:
	The topics below delineate the various target references that are available within each context.		The topics below delineate the various target references that are available within each context.

	*~~{{fl\|~~Container Target References}}		*[[Container Target References\|Container Context#references]]
	*~~{{fl\|~~Hero Target References}}		*[[Hero Target References\|Hero Context#references]]
	*~~{{fl\|~~Pick Target References}}		*[[Pick Target References\|Pick Context#references]]
	*~~{{fl\|~~Thing Target References}}		*[[Thing Target References\|Thing Context#references]]
	*~~{{fl\|~~Field Target References}}		*[[Field Target References\|Field Context#references]]
	*~~{{fl\|~~Pool Target References}}		*[[Pool Target References\|Pool Context#references]]
	*~~{{fl\|~~Scene Target References}}		*[[Scene Target References\|Scene Context#references]]
	*~~{{fl\|~~Layout Target References}}		*[[Layout Target References\|Layout Context#references]]
	*~~{{fl\|~~Template Target References}}		*[[Template Target References\|Template Context#references]]
	*~~{{fl\|~~Portal Target References}}		*[[Portal Target References\|Portal Context#references]]
	*~~{{fl\|~~Value Target References}}		*[[Value Target References\|Value Context#references]]
	*~~{{fl\|~~Table Target References}}		*[[Table Target References\|Table Context#references]]
	*~~{{fl\|~~State Target References}}		*[[State Target References\|State Context#references]]