Special Symbols - Revision history

Rob at 11:36, 4 December 2008

2008-12-04T11:36:10Z

← Older revision		Revision as of 11:36, 4 December 2008
Line 1:		Line 1:
	{{context\|~~Basic Concepts and Terminology\|Scripting Language\|Language Basics~~}}		{{context\|Kit Reference}}

	Many scripts have special pieces of information that are either passed into the script from HL or that the script must specify for subsequent use by HL. For example, a script-based label portal has two such values. On entry, the script is informed whether it is being applied to either a thing or a pick, since that distinction is important for some scripts. On exit, the script must tell HL what the final text is that should be displayed within the label.		Many scripts have special pieces of information that are either passed into the script from HL or that the script must specify for subsequent use by HL. For example, a script-based label portal has two such values. On entry, the script is informed whether it is being applied to either a thing or a pick, since that distinction is important for some scripts. On exit, the script must tell HL what the final text is that should be displayed within the label.

Rob at 08:33, 22 November 2008

2008-11-22T08:33:21Z

← Older revision		Revision as of 08:33, 22 November 2008
Line 1:		Line 1:
	~~[[Category:~~Basic Concepts and Terminology]]		{{context\|Basic Concepts and Terminology\|Scripting Language\|Language Basics}}
	~~[Context: [[Home~~\|~~HL Kit]] [[Basic Concepts and Terminology]] [[~~Scripting Language~~]] [[~~Language Basics~~]]]~~

	Many scripts have special pieces of information that are either passed into the script from HL or that the script must specify for subsequent use by HL. For example, a script-based label portal has two such values. On entry, the script is informed whether it is being applied to either a thing or a pick, since that distinction is important for some scripts. On exit, the script must tell HL what the final text is that should be displayed within the label.		Many scripts have special pieces of information that are either passed into the script from HL or that the script must specify for subsequent use by HL. For example, a script-based label portal has two such values. On entry, the script is informed whether it is being applied to either a thing or a pick, since that distinction is important for some scripts. On exit, the script must tell HL what the final text is that should be displayed within the label.

Rob: New page: Category:Basic Concepts and Terminology [Context: HL Kit … Basic Concepts and Terminology … Scripting Language … Language Basics] Many scripts have...

2008-11-18T10:06:40Z

New page: Category:Basic Concepts and Terminology [Context: HL Kit � Basic Concepts and Terminology � Scripting Language � Language Basics] Many scripts have...

New page

[[Category:Basic Concepts and Terminology]]
[Context: [[Home|HL Kit]]  [[Basic Concepts and Terminology]]  [[Scripting Language]]  [[Language Basics]]]

Many scripts have special pieces of information that are either passed into the script from HL or that the script must specify for subsequent use by HL. For example, a script-based label portal has two such values. On entry, the script is informed whether it is being applied to either a thing or a pick, since that distinction is important for some scripts. On exit, the script must tell HL what the final text is that should be displayed within the label.

Whenever a value needs to be passed into or out of a script, a "special symbol" is used. Special symbols behave exactly like variables, so they can be used just like a variable within the script. The name of each special symbol is always prefixed with the '@' character, which is followed by the name of the special symbol. For example, to access the special symbol "value", the syntax would be "@value".

The set of special symbols varies for each script, as will their use, with some scripts having zero special symbols and a few having many. The exact symbols for a given script are specified with the details for each script within in [[Kit Reference]] documentation.