Context Transitions

Context: HL Kit … Kit Reference 

Overview

Every script begins with an initial context that is dictated by the particular script. Quite often, though, you'll want to access information somewhere else within the data hierarchy. That's when context transitions come into play. A context transition allows you to move through the hierarchy, progressing to objects either above or below the current context. These transitions can be chained, allowing you to move through a sequence of contexts to reach the desired destination.

NOTE! If transitions are utilized that result in an invalid (i.e. non-existent) context, any subsequent target reference will be invalid. 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.

Using "this"

Every script has an initial context that is automatically established (see the specific script to know what it is). Normally, this context is implied, so you don't need to do anything to reference that context. However, some authors will want their scripts to clearly indicate when the implied context is being used. To accommodate this, scripts can utilize the reserved word "this" to indicate the implied context.

For example, an Eval Script starts with the pick as its implied context. So you could write a target identifier that checks the validity of that pick as simply "valid". Alternately, you could specify "this" as the context, yielding a target identifier of "this.valid". Either method is perfectly legal and you are welcome to use whichever method you prefer.

NOTE! The "this" reference identifies the implied context only. Therefore, you can only use "this" as the first context reference for a target identifier. If "this" is used anywhere else, a compilation error will occur.

Topics

From within a given context, you are only able to transition to a specific set of other contexts. The topics below identify what the valid transitions are for each context.

• Container Context Transitions
• Hero Context Transitions
• Pick Context Transitions
• Thing Context Transitions
• Field Context Transitions
• Pool Context Transitions
• Scene Context Transitions
• Layout Context Transitions
• Template Context Transitions
• Portal Context Transitions
• Value Context Transitions
• Table Context Transitions
• State Context Transitions

Container Context

From within a "container" context, you can utilize the following set of valid context transitions:

state	Transitions to the state context. Example: this.state
hero	Transitions to the hero context corresponding to the hero that is the parent of the current container. If the current container is a hero, then this transition changes nothing but does resolve successfully. Example: this.hero
container	Transitions to the container context corresponding to whatever container is the immediate parent of the current container. If the current container is a hero, then the transition fails to resolve. Example: this.container
parent	Transitions to the pick context corresponding to the parent pick that attaches the container. If the container is a hero and has no parent pick, the transition fails to resolve. Example: this.parent
child[id]	Transitions to the pick context corresponding to the first pick within the container that derives from the thing with the id specified. If the container has no child pick with the given unique id, a run-time error notification is reported to the user and the transition fails to resolve. Example: this.child[mypick]
childfound[id]	Transitions to the pick context corresponding to the first pick within the container that derives from the thing with the id specified. This transition is identical to "child[id]", except that the existence of the child pick is optional. If the child is found, the transition occurs normally. If the child does not exist, no run-time error is reported, although the transition still fails to resolve. Example: this.childfound[mypick]
firstchild[expr,sort]	Transitions to the pick context corresponding to the first pick within the container that satisfies the tag expression given by expr. Since multiple children may satisfy the tag expression, an optional sort set id may be specified by sort, resulting in all matching children being sorted and the first child being used after the sort is performed. The tag expression may be either a literal string or a string expression. If no matching child exists, the transition fails to resolve. Example: this.firstchild[expr,mysort] Example: this.firstchild[expr]
anchor	Transitions to the pick context corresponding to the pick within the master actor that attaches the current actor as a minion. If the container does not reside within a minion, the transition fails to resolve. Example: this.anchor
master	Transitions to the hero context corresponding to the master actor for which this container is a minion. If the container is not a minion, the transition fails to resolve. Example: this.master
minion[id]	Transitions to the hero context corresponding to the minion actor with the given id that exists beneath the actor that possesses the current container. If the container is not a master or the specified minion does not exist, the transition fails to resolve. Example: this.minion[myminion]
herofield[id]	Transitions to the field context corresponding to the field given by id that exists on the "actor" pick for the containing actor. This is a shorthand notation for "hero.child[actor].field[id]". Example: this.herofield[myfield]
usagepool[id]	Transitions to the pool context corresponding to the usage pool given by id that exists within the current container. This transition is only valid for actors, since gizmos do not possess usage pools. Example: this.usagepool[mypool]
transact	Transitions to the pick context corresponding to the transaction pick that is associated with the hero governing the current context. Example: this.transact NOTE! The transaction pick is only utilized within buy and sell transactions. As such, this transition is only valid within a few select scripts.
dynalink[index]	Transitions to the pick context corresponding to the registered dynamic linkage with the index specified. If no dynamic linkage has been registered with the given index, the transition fails to resolve. The index may be an arithmetic expression that calculates the actual index value to be used. Example: this.dynalink[myindex]

Hero Context

A "hero" context is very similar to a "container" context, except that the options available are a bit more limited (e.g. heroes don't have parents). From within a "hero" context, you can utilize the following set of valid context transitions:

state	Transitions to the state context. Example: this.state
child[id]	Transitions to the pick context corresponding to the first pick within the container that derives from the thing with the id specified. If the container has no child pick with the given unique id, a run-time error notification is reported to the user and the transition fails to resolve. Example: this.child[mypick]
childfound[id]	Transitions to the pick context corresponding to the first pick within the container that derives from the thing with the id specified. This transition is identical to "child[id]", except that the existence of the child pick is optional. If the child is found, the transition occurs normally. If the child does not exist, no run-time error is reported, although the transition still fails to resolve. Example: this.childfound[mypick]
firstchild[expr,sort]	Transitions to the pick context corresponding to the first pick within the container that satisfies the tag expression given by expr. Since multiple children may satisfy the tag expression, an optional sort set id may be specified by sort, resulting in all matching children being sorted and the first child being used after the sort is performed. The tag expression may be either a literal string or a string expression. If no matching child exists, the transition fails to resolve. Example: this.firstchild[expr,mysort] Example: this.firstchild[expr]
minion[id]	Transitions to the hero context corresponding to the minion actor with the given id that exists beneath the actor that possesses the current container. If the container is not a master or the specified minion does not exist, the transition fails to resolve. Example: this.minion[myminion]
herofield[id]	Transitions to the field context corresponding to the field given by id that exists on the "actor" pick for the containing actor. This is a shorthand notation for "hero.child[actor].field[id]". Example: this.herofield[myfield]
usagepool[id]	Transitions to the pool context corresponding to the usage pool given by id that exists within the current actor. Example: this.usagepool[mypool]
transact	Transitions to the pick context corresponding to the transaction pick that is associated with the hero governing the current context. Example: this.transact NOTE! The transaction pick is only utilized within buy and sell transactions. As such, this transition is only valid within a few select scripts.
dynalink[index]	Transitions to the pick context corresponding to the registered dynamic linkage with the index specified. If no dynamic linkage has been registered with the given index, the transition fails to resolve. The index may be an arithmetic expression that calculates the actual index value to be used. Example: this.dynalink[myindex]

Pick Context

From within a "pick" context, you can utilize the following set of valid context transitions:

state	Transitions to the state context. Example: this.state
hero	Transitions to the hero context corresponding to the hero that contains the current pick. Example: this.hero
container	Transitions to the container context corresponding to the immediate container of the current pick, whether it be a hero or a gizmo. Example: this.container
parent	Transitions to the container context corresponding to the immediate container of the current pick, just like the "container" transition. Example: this.parent
gizmo	Transitions to the container context corresponding to the child gizmo directly attached by the pick. If the pick has no attached child gizmo, the transition fails to resolve. Example: this.gizmo
field[id]	Transitions to the field context corresponding to the field within the current pick that has the id specified. If the given field does not exist for the current pick, the transition fails to resolve. Example: this.field[myfield] NOTE! Within things and picks, there are a number of pre-defined pseudo-fields that are always defined and that allow access to facets of the pick that are not governed by user-defined fields. These pseudo-fields behave like normal fields in all respects within scripts, except that some are read-only. The list of pre-defined fields can be found elsewhere in the Kit Reference documentation.
root	Transitions to the pick context corresponding to the root pick that bootstraps the current pick into the container. If the current pick is not bootstrapped, or if the current pick is designated as unique and can possess multiple bootstraps, the transition fails to resolve. Example: this.source
gearholder	Transitions to the pick context corresponding to the pick that is assigned as the gear holder of the current pick. If the current pick is not held, the transition fails to resolve. If the current pick is not gear, an error is reported and the transition fails to resolve. Example: this.gearholder
linkage[id]	Transitions to the pick context corresponding to the linkage with the id specified. If the linkage is not defined, an error is reported. Example: this.linkage[mylink]
anchor	Transitions to the pick context corresponding to the pick within the master actor that attaches the current actor as a minion. If the pick does not reside within a minion, the transition fails to resolve. Example: this.anchor
master	Transitions to the hero context corresponding to the master actor for which this pick's container is a minion. If the pick is not within a minion, the transition fails to resolve. Example: this.master
minion[id]	Transitions to the hero context corresponding to the minion actor with the given id that exists beneath the actor that possesses the current pick. The id can be omitted, in which case the minion is implicitly identified and must be directly attached by the current pick. If the pick does not reside within a master or the specified minion does not exist, the transition fails to resolve. Example: this.minion[myminion] Example: this.minion
herofield[id]	Transitions to the field context corresponding to the field given by id that exists on the "actor" pick for the containing actor. This is a shorthand notation for "hero.child[actor].field[id]". Example: this.herofield[myfield]
usagepool[id]	Transitions to the pool context corresponding to the usage pool with the id specified for the current pick. Example: this.usagepool[mypool]
shadow	Transitions to the container context corresponding to the container into which the current pick is shadowed. If the pick is not shadowed, an error is reported and the transition fails to resolve. Example: this.shadow
origin	Transitions to the container context corresponding to the container into which the current pick was originally added. If the pick is displaced, the container is where the pick was added by the user. If not displaced, the container is simply the container for the pick. Example: this.origin

Thing Context

A "thing" context is very similar to a "pick" context, except that a "thing" context represents a thing that has not yet been added to a container and therefore lacks any dynamic state. As a result, the "thing" context is much more restrictive than the "pick" context. From within a "thing" context, you can utilize the following set of valid context transitions:

state	Transitions to the state context. Example: this.state
hero	Transitions to the hero context corresponding to the hero that the thing will be potentially added to. Example: this.hero
field[id]	Transitions to the field context corresponding to the field within the current thing that has the id specified. If the given field does not exist for the current thing, the transition fails to resolve. Example: this.field[myfield] NOTE! Within things and picks, there are a number of pre-defined pseudo-fields that are always defined and that allow access to facets of the pick that are not governed by user-defined fields. These pseudo-fields behave like normal fields in all respects within scripts, except that some are read-only. The list of pre-defined fields can be found elsewhere in the Kit Reference documentation.
linkage[id]	Transitions to the pick context corresponding to the linkage with the id specified. If the linkage is not defined, an error is reported. Example: this.linkage[mylink]

Field Context

From within a "field" context, you can utilize the following set of valid context transitions:

state	Transitions to the state context. Example: this.state
pick	Transitions to the pick context corresponding to the pick that contains the current field. Example: this.pick
chosen	Transitions to either the pick context corresponding to the user-selected pick stored within the field or the thing context corresponding to the user-selected thing stored within the field, depending on the nature of the field. The transition is only valid for use on fields that store menu selections made by the user. Example: this.chosen

Pool Context

From within a "pool" context, you can utilize the following set of valid context transitions:

-None-

There are no transitions from within a pool context.

Scene Context

From within a "scene" context, you can utilize the following set of valid context transitions:

layout[id]	Transitions to the layout context corresponding to the layout within the current scene that possesses the id specified. If the layout does not exist within the scene, the transition fails to resolve. Example: this.layout[mylayout]
container	Transitions to the container context corresponding to the container to which the scene applies, whether it be an actor or a gizmo. Example: this.container NOTE! After transitioning, access within the new container context will be read-only and limited in what information can be retrieved. NOTE! This transition can only be used as the first transition when within a visual script.
hero	Transitions to the hero context corresponding to the hero to which the scene applies. Example: this.hero NOTE! After transitioning, access within the new hero context will be read-only and limited in what information can be retrieved. NOTE! This transition can only be used as the first transition when within a visual script.

Layout Context

From within a "layout" context, you can utilize the following set of valid context transitions:

parent	Transitions to the scene context corresponding to the visual element that contains the layout. Example: this.parent
template[id]	Transitions to the template context corresponding to the template within the current layout that possesses the id specified. If the template does not exist within the layout, the transition fails to resolve. Example: this.template[mytemplate] NOTE! The id specified is the id of the template reference, as defined within the layout, and not necessarily the id of the template itself.
portal[id]	Transitions to the portal context corresponding to the portal within the current layout that possesses the id specified. If the portal does not exist within the layout, the transition fails to resolve. Example: this.portal[myportal] NOTE! The id specified is the id of the portal reference, as defined within the layout, and not necessarily the id of the portal itself. NOTE! Only portals defined directly within the layout can be accessed via this transition. Portals within templates must be accessed via the template.
container	Transitions to the container context corresponding to the container to which the layout applies, whether it be an actor or a gizmo. Example: this.container NOTE! After transitioning, access within the new container context will be read-only and limited in what information can be retrieved. NOTE! This transition can only be used as the first transition when within a visual script.
hero	Transitions to the hero context corresponding to the hero to which the layout applies. Example: this.hero NOTE! After transitioning, access within the new hero context will be read-only and limited in what information can be retrieved. NOTE! This transition can only be used as the first transition when within a visual script.

Template Context

From within a "template" context, you can utilize the following set of valid context transitions:

parent	Transitions to the layout context or table context corresponding to the visual element that contains the tmeplate. Example: this.parent NOTE! The "parent" transition can only be utilized a single time, so it is not possible to go upwards two or more levels within the hierarchy.
portal[id]	Transitions to the portal context corresponding to the portal within the current template that possesses the id specified. If the portal does not exist within the template, the transition fails to resolve. Example: this.portal[myportal] NOTE! Only portals defined directly within the template can be accessed via this transition.
field[id]	Transitions to the value context corresponding to the field within the current template that has the id specified. The fields for a template are dictated by the pick or thing that is associated with the template. If the given field does not exist for the pick/thing, the transition fails to resolve. Example: this.field[myfield] NOTE! Within templates, all fields are treated as read-only, which is controlled by transitioning to a distinct "value" context instead of "field" context.
container	Transitions to the container context corresponding to the container to which the template applies, whether it be an actor or a gizmo. Example: this.container NOTE! After transitioning, access within the new container context will be read-only and limited in what information can be retrieved. NOTE! This transition can only be used as the first transition when within a visual script.
hero	Transitions to the hero context corresponding to the hero to which the template applies. Example: this.hero NOTE! After transitioning, access within the new hero context will be read-only and limited in what information can be retrieved. NOTE! This transition can only be used as the first transition when within a visual script.

Portal Context

From within a "portal" context, you can utilize the following set of valid context transitions:

parent

Transitions to the layout context or template context corresponding to the visual element that contains the portal. Example: this.parent NOTE! The "parent" transition can only be utilized a single time, so it is not possible to go upwards two or more levels within the hierarchy.

Value Context

The "value" context parallels a "field" context, with the key distinction being that all values are read-only, since they are intended for display only. From within a "value" context, you can utilize the following set of valid context transitions:

-None-

There are no transitions from within a value context.

Table Context

The "table" context is essentially the same as a "portal" context, since the context simply corresponds to a table portal within a layout. From within a "table" context, you can utilize the following set of valid context transitions:

parent

Transitions to the layout context corresponding to the visual element that contains the portal. Example: this.parent NOTE! The "parent" transition can only be utilized a single time, so it is not possible to go upwards two or more levels within the hierarchy.

State Context

From within a "state" context, you can utilize the following set of valid context transitions:

-None-

There are no transitions from within a state context.

Special Contexts

Within some scripts, special contexts are supported. These special contexts behave the same way within any script that uses them. However, what they correspond to may be different within each script. The specific scripts where special contexts can be used will explicitly cite the availability of the context in their description. Alternately, some special contexts can be established within a script via certain language mechanisms (e.g. "eachpick"). The behavior of these contexts is outlined below.

eachpick	The "eachpick" context only applies within the context of a "foreach" statement and represents the pick that is currently being iterated upon by the "foreach" statement. The current pick is accessed via the "eachpick." initial context. When used, the script context is switched to the iterated pick, and all subsequent actions are performed relative to that pick.
altpick	The "altpick" context represents an alternate pick that is integral to the script and can be accessed readily. The alternate pick is accessed via the "altpick." initial context. When used, the script context is switched to the alternate pick, and all subsequent actions are performed relative to that pick.
altthing	The "altthing" context represents an alternate thing that is integral to the script and can be accessed readily. The alternate thing is accessed via the "altthing." initial context. When used, the script context is switched to the alternate thing, and all subsequent actions are performed relative to that thing.
focus	The "focus" context only applies when the "setfocus" target reference is utilized on a pick context to establish that pick as a memorized context. The established focus pick context is accessed via the "focus." initial context, after which the script context changes to that pick and all subsequent actions are performed relative to that pick.
actor	The "actor" context only applies when the "setactor" target reference is utilized on a hero context to establish that hero as a memorized context. The established actor context is accessed via the "actor." initial context, after which the script context changes to that actor and all subsequent actions are performed relative to that actor. IMPORTANT! This is a situation where there is a critical distinction between "hero" and "actor". The "actor" context only applies to whatever actor has been established as the "actor focus".
transaction	The "transaction" context represents an alternate pick that is integral to scripts involved in buy and sell transactions of objects. The alternate pick is accessed via the "transaction." initial context. When used, the script context is switched to the alternate pick, and all subsequent actions are performed relative to that pick.

IMPORTANT! All special contexts must be specified at the start of an identifier. If not, they will not be acknowledged by the compiler. For example, if the "altpick" special context is supported by a script, the reference "altpick.field[livename].text" would work perfectly. However, the reference "this.altpick.field[livename].text" would fail to compile, since "altpick." is not given as the initial context for the identifier.