DiagramElements-FreezeValue/en - Versionsgeschichte

Cg: /* Bytes (ByteArray) */

2026-04-25T08:02:44Z

Bytes (ByteArray)

← Nächstältere Version		Version vom 25. April 2026, 08:02 Uhr
Zeile 80:		Zeile 80:
	* hex format: "<code>xxXXxxXX</code>" (two hex characters per byte; no spaces in-between)		* hex format: "<code>xxXXxxXX</code>" (two hex characters per byte; no spaces in-between)
	* hex format: "<code>xx XX xx XX</code>" (two hex characters per byte; with spaces in-between)		* hex format: "<code>xx XX xx XX</code>" (two hex characters per byte; with spaces in-between)

			=== Arrays (Sequenceables) ===
			given that elements el1, el2, ... elN can be represented as literal constants (i.e. Strings, numbers, bytes or arrays), a sequence of them can be
			written as:
			* Smalltalk format: "<code>#( el1 el2 ... elN )</code> (with spaces between elements).
			* JSON format: "<code>[ el1 , el2 , ... , elN ]</code>

	=== Geometric Objects (Points and Rectangles) ===		=== Geometric Objects (Points and Rectangles) ===

Cg: /* String */

2026-04-24T19:22:46Z

String

← Nächstältere Version		Version vom 24. April 2026, 19:22 Uhr
Zeile 67:		Zeile 67:
	In addition, variables of the form "<code>%(xxx)</code>" are expanded by the value of the input pin named "xxx". This expansion is also controlled by a flag in the popup menu.		In addition, variables of the form "<code>%(xxx)</code>" are expanded by the value of the input pin named "xxx". This expansion is also controlled by a flag in the popup menu.

	Freeze value expansion can be suppressed either in the ~~basket itself~~ (the freeze-menu),		Freeze value expansion can be suppressed either at the pin (see the freeze-menu),
	or globally via a flag in the project, to ~~enforce~~ ~~backward~~ ~~compatibility~~ of a ~~whole~~ ~~library~~ (in the rare situation, that an older library depends on such freeze values being unchanged).		or globally via a flag in the project or import library. Global disabling is discouraged and only to be used for backward compatibility (in the rare situation, that an older library depends on such freeze values being unchanged).

	Be reminded, that these variable expansions are only done for freeze values. If the value comes from another pin, it is passed unchanged.		Be reminded, that these variable expansions are only done for freeze values. If the value comes from another pin, it is passed unchanged.

Cg: /* Float */

2026-04-24T19:19:23Z

Float

← Nächstältere Version		Version vom 24. April 2026, 19:19 Uhr
Zeile 29:		Zeile 29:
	You can force single precision floats by using the 'f' exponent indicator.		You can force single precision floats by using the 'f' exponent indicator.

	* double precision floats such as: "<code>123.0</code>", "<code>+123.0</code>", "<code>-123.0</code>", "<code>.123</code>", "<code>123.</code>", "<code>123.0e+2</code>", "<code>123.0e-2</code>"		* double precision (64bit) floats such as: "<code>123.0</code>", "<code>+123.0</code>", "<code>-123.0</code>", "<code>.123</code>", "<code>123.</code>", "<code>123.0e+2</code>", "<code>123.0e-2</code>"

	* single precision: "<code>123.0f+2</code>" or "<code>-123.0f</code>"		* single precision (32 bit): "<code>123.0f+2</code>" or "<code>-123.0f</code>"

	* extended precision: "<code>123.0q+2</code>" or "<code>-123.0q</code>"		* extended precision (80+ bit): "<code>123.0q+2</code>" or "<code>-123.0q</code>"

			* quadruple precision (128 bit): "<code>123.0Q+2</code>" or "<code>-123.0Q</code>"

	Do not expect any speed or other advantages when using single precision floats. Actually, expect problems due to larger errors, non-stable series computations etc. Use them only if you need to emulate less precise computations.		Do not expect any speed or other advantages when using single precision floats. Actually, expect problems due to larger errors, non-stable series computations etc. Use them only if you need to emulate less precise computations.

	Extended precision floats may not be supported by all CPU types (these use the underlying machine's "long double" data type, which is either an 80-bit extended IEEE or a 128-bit quadruple IEEE float (eg. on Sparc CPUs). Not all CPUs do support these and we can not guarantee that future machines will dp. However, currently all supported architectures do.		Extended precision floats may not be supported by all CPU types (these use the underlying machine's "long double" data type, which is either an 80-bit extended IEEE or a 128-bit quadruple IEEE float (eg. on Sparc CPUs). Not all CPUs do support these and we can not guarantee that future machines will dp. However, currently all supported architectures do.

			Notice that depending on the CPU, quadruple precision arithmetic might be performed by software and will therefore be slow (currently the case for all supported architectures)

	=== String ===		=== String ===

Cg: /* Float */

2026-04-24T19:16:04Z

Float

← Nächstältere Version		Version vom 24. April 2026, 19:16 Uhr
Zeile 37:		Zeile 37:
	Do not expect any speed or other advantages when using single precision floats. Actually, expect problems due to larger errors, non-stable series computations etc. Use them only if you need to emulate less precise computations.		Do not expect any speed or other advantages when using single precision floats. Actually, expect problems due to larger errors, non-stable series computations etc. Use them only if you need to emulate less precise computations.

	Extended precision floats may not be supported by all CPU types (these use the underlying machine's "long double" data type, which is either an 80-bit extended IEEE or a 128-bit quadruple IEEE float. As ~~not~~ all CPUs do support these, we ~~cannot~~ guarantee that future machines will ~~support them~~. However, currently all supported ~~machine~~ architectures do.		Extended precision floats may not be supported by all CPU types (these use the underlying machine's "long double" data type, which is either an 80-bit extended IEEE or a 128-bit quadruple IEEE float (eg. on Sparc CPUs). Not all CPUs do support these and we can not guarantee that future machines will dp. However, currently all supported architectures do.

	=== String ===		=== String ===

Cg: /* Introduction */

2026-04-24T12:33:25Z

Introduction

← Nächstältere Version		Version vom 24. April 2026, 12:33 Uhr
Zeile 3:		Zeile 3:
	A so called "''Freeze Value''" is a constant value attached to an input pin.		A so called "''Freeze Value''" is a constant value attached to an input pin.
	When executed, that value will be presented to the action. Pins with such a constant input are referred to as "''frozen pins''" in expecco.		When executed, that value will be presented to the action. Pins with such a constant input are referred to as "''frozen pins''" in expecco.

			The freeze value can be either specified as a literal (textual) constant, or be provided by a variable (from an environment which is visible at the time the step is active).

	Be aware, that frozen pin values should normally not be consumed;		Be aware, that frozen pin values should normally not be consumed;
Zeile 10:		Zeile 12:
	Thus, the diagram editor will automatically change the pin's behavior to non-triggering and non-consuming (i.e. make it a "''parameter pin''").		Thus, the diagram editor will automatically change the pin's behavior to non-triggering and non-consuming (i.e. make it a "''parameter pin''").

	The following describes the data format and syntax used in pin freeze values.		The following describes the data format and syntax used for pin freeze values.
	In general, the text entered as freeze value is parsed by the input pin's datatype.		In general, the text entered as freeze value is parsed by the input pin's datatype, or if it is provided by a variable, that variable's data type.

	== Format for Particular Types ==		== Format for Particular Types ==

Cg: /* Introduction */

2026-04-24T12:29:35Z

Introduction

← Nächstältere Version		Version vom 24. April 2026, 12:29 Uhr
Zeile 2:		Zeile 2:

	A so called "''Freeze Value''" is a constant value attached to an input pin.		A so called "''Freeze Value''" is a constant value attached to an input pin.
	When executed, that value will be presented to the action.		When executed, that value will be presented to the action. Pins with such a constant input are referred to as "''frozen pins''" in expecco.

	Be aware, that frozen pin values should normally not be consumed;		Be aware, that frozen pin values should normally not be consumed;

Sv: /* $(...) Expansion */

2023-05-15T09:45:51Z

$(...) Expansion

← Nächstältere Version		Version vom 15. Mai 2023, 09:45 Uhr
Zeile 106:		Zeile 106:
	* ExecutionDirectory - a temporary directory, which vanishes after the execution		* ExecutionDirectory - a temporary directory, which vanishes after the execution
	* ExpeccoInstallationDirectory - the directory, where expecco was installed		* ExpeccoInstallationDirectory - the directory, where expecco was installed
	* ExpeccoLibraryDirectory - the directory, where the libraries delivered with expecco live		* ExpeccoLibraryDirectory - the directory, where the libraries delivered with expecco live (first supported in 23.1)
	* ExpeccoPluginDirectory - the directory, where expecco's plugins are installed		* ExpeccoPluginDirectory - the directory, where expecco's plugins are installed
	* ProjectDirectory - the temporary project directory		* ProjectDirectory - the temporary project directory

Sv: /* Variable Expansion */

2023-05-15T09:45:15Z

Variable Expansion

← Nächstältere Version		Version vom 15. Mai 2023, 09:45 Uhr
Zeile 106:		Zeile 106:
	* ExecutionDirectory - a temporary directory, which vanishes after the execution		* ExecutionDirectory - a temporary directory, which vanishes after the execution
	* ExpeccoInstallationDirectory - the directory, where expecco was installed		* ExpeccoInstallationDirectory - the directory, where expecco was installed
			* ExpeccoLibraryDirectory - the directory, where the libraries delivered with expecco live
	* ExpeccoPluginDirectory - the directory, where expecco's plugins are installed		* ExpeccoPluginDirectory - the directory, where expecco's plugins are installed
	* ProjectDirectory - the temporary project directory		* ProjectDirectory - the temporary project directory

Cg: /* $(...) Expansion */

2023-04-25T18:16:28Z

$(...) Expansion

← Nächstältere Version		Version vom 25. April 2023, 18:16 Uhr
Zeile 115:		Zeile 115:
	* LoginName - your login name (username under Unix/Linux/OSX)		* LoginName - your login name (username under Unix/Linux/OSX)
	* UserName - your full name (if known, otherwise the login name)		* UserName - your full name (if known, otherwise the login name)

	* <''inPinName''> - where inPinName is the name of an input pin of the containing compound action		* <''inPinName''> - where inPinName is the name of an input pin of the containing compound action

Cg: /* Variable Expansion */

2022-03-08T16:04:21Z

Variable Expansion

← Nächstältere Version		Version vom 8. März 2022, 16:04 Uhr
Zeile 97:		Zeile 97:
	== Variable Expansion ==		== Variable Expansion ==

	Inside a freeze value, variable values can be embedded using the "$(...)" ~~and "%(...)" notations~~,		Inside a freeze value, variable values can be embedded using the "$(...)" notation,
	unless the freeze value has the "''No Variable Expansion'' flag set via the freeze value's popup menu).		unless the freeze value has the "''No Variable Expansion'' flag set via the freeze value's popup menu).

Zeile 115:		Zeile 115:
	* LoginName - your login name (username under Unix/Linux/OSX)		* LoginName - your login name (username under Unix/Linux/OSX)
	* UserName - your full name (if known, otherwise the login name)		* UserName - your full name (if known, otherwise the login name)
			* <''inPinName''> - where inPinName is the name of an input pin of the containing compound action

	If the script must run somewhere else, you can provide the path at the block's "''execDir''" input pin (or for shell scripts, you can also specify it in the editor, which is effectively defining the directory as a freeze value). The execution directory pathname (provided at the pin) may contain placeholders in the form "$(xxx)", where "xxx" is either a shell environment variable, or one of the above listed builtin placeholder variables.		If the script must run somewhere else, you can provide the path at the block's "''execDir''" input pin (or for shell scripts, you can also specify it in the editor, which is effectively defining the directory as a freeze value). The execution directory pathname (provided at the pin) may contain placeholders in the form "$(xxx)", where "xxx" is either a shell environment variable, or one of the above listed builtin placeholder variables.

	=== %(...) Expansion ===
	Variables of the form "%(xxx)" are expanded by the value of the input pin named "xxx".
	This expansion is also controlled by the ''No Variable Expansion'' flag in the popup menu.

	== Popup Menu ==		== Popup Menu ==