Difference between revisions of "Target References"
(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 ...) |
|||
| Line 3: | Line 3: | ||
==Overview== | ==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 | + | 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. | {{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. | ||
| + | |||
| + | ==Topics== | ||
| + | |||
| + | The topics below delineate the various target references that are available within each context. | ||
| + | |||
| + | *{{fl|Container Target References}} | ||
| + | *{{fl|Hero Target References}} | ||
| + | *{{fl|Pick Target References}} | ||
| + | *{{fl|Thing Target References}} | ||
| + | *{{fl|Field Target References}} | ||
| + | *{{fl|Pool Target References}} | ||
| + | *{{fl|Scene Target References}} | ||
| + | *{{fl|Layout Target References}} | ||
| + | *{{fl|Template Target References}} | ||
| + | *{{fl|Portal Target References}} | ||
| + | *{{fl|Value Target References}} | ||
| + | *{{fl|Table Target References}} | ||
| + | *{{fl|State Target References}} | ||
Revision as of 03:11, 5 December 2008
Context: HL Kit … 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.
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.
Topics
The topics below delineate the various target references that are available within each context.
- Container Target References
- Hero Target References
- Pick Target References
- Thing Target References
- Field Target References
- Pool Target References
- Scene Target References
- Layout Target References
- Template Target References
- Portal Target References
- Value Target References
- Table Target References
- State Target References
