DiagramElements-FreezeValue/en - Versionsgeschichte

Cg: /* Any */

2026-06-09T02:29:40Z

Any

← Nächstältere Version		Version vom 9. Juni 2026, 02:29 Uhr
Zeile 109:		Zeile 109:
	* <code>1234.56</code> - will be a float value		* <code>1234.56</code> - will be a float value
	* <code>'1234'</code> - will be a string value		* <code>'1234'</code> - will be a string value
			in contrast, a freeze value of a string-typed pin should NOT have quotes around.

	== Variable Expansion ==		== Variable Expansion ==

Cg: /* Float */

2026-05-26T22:06:27Z

Float

← Nächstältere Version		Version vom 26. Mai 2026, 22:06 Uhr
Zeile 30:		Zeile 30:

	By default, floats are represented as double-precision IEEE limited precision rationals (64 bit).		By default, floats are represented as double-precision IEEE limited precision rationals (64 bit).
	You can force single precision floats by using the 'f' exponent indicator.		You can force single precision floats by using the 'f' exponent indicator (or an 'f' suffix).

	* 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>"		* 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>"
Zeile 40:		Zeile 40:
	* quadruple precision (128 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 (depends on the CPU). 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. 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)		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)

Cg: /* Integer */

2026-05-02T18:05:00Z

Integer

← Nächstältere Version		Version vom 2. Mai 2026, 18:05 Uhr
Zeile 22:		Zeile 22:

	* decimal (for example: "<code>1234</code>" , "<code>-1234</code>)		* decimal (for example: "<code>1234</code>" , "<code>-1234</code>)
	* with Smalltalk radix prefix: (for example: "<code>16rCAFE</code>" , "<code>16r-AA</code>, "<code>8r100</code>, "<code>2r101010000</code>) ~~any radix between 2 and 36 is allowed~~.		* with Smalltalk radix prefix: (for example: "<code>16rCAFE</code>" , "<code>16r-AA</code>, "<code>8r100</code>, "<code>2r101010000</code>).
			::Any radix between 2 and 36 is allowed.
	* with C radix prefix: (for example: "<code>0xCAFE</code>" , "<code>-0xAA</code>, "<code>0b101010000</code>) ("0x" for hex, "0o" for octal and "0b" for binary~~).<br>Notice that the C-octal notation (prefix 0) is not supported (ie. "<code>0377</code>" will be read as 377~~).		* with C radix prefix: (for example: "<code>0xCAFE</code>" , "<code>-0xAA</code>, "<code>0b101010000</code>) ("0x" for hex, "0o" for octal and "0b" for binary).
			::Notice that the C-octal notation (prefix 0) is not supported<br>(ie. "<code>0377</code>" will be read as 377).

	=== Float ===		=== Float ===

Cg: /* Introduction */

2026-05-02T18:03:13Z

Introduction

← Nächstältere Version		Version vom 2. Mai 2026, 18:03 Uhr
Zeile 11:		Zeile 11:

	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''").
			<br>You can also change the pin's behavior via its context menu ("''Make Parameter Pin''") or with the keyboard shortcut <kbd>CTRL-p</kbd>.

	The following describes the data format and syntax used for pin freeze values.		The following describes the data format and syntax used for pin freeze values (which btw. is also used for environment variables).
	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.		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.

Cg: /* String */

2026-04-29T06:02:34Z

String

← Nächstältere Version		Version vom 29. April 2026, 06:02 Uhr
Zeile 46:		Zeile 46:

	If the pin's datatype is <CODE>String</code>, then no leading/trailing single quotes are needed.		If the pin's datatype is <CODE>String</code>, then no leading/trailing single quotes are needed.
	In fact, if there are quotes, these will be part of the string. <br>However, '''quotes are needed''' if the type is not unambiguously a String type (i.e. Any or a Union type).		<br>In fact, if there are quotes, these will be part of the string. <br>However, '''quotes are needed''' if the type is not unambiguously a String type (i.e. Any or a Union type).

	By default, NO C-style escape sequences are interpreted - i.e. the string is taken "as-is".		By default, NO C-style escape sequences are interpreted - i.e. the string is taken "as-is".

Cg: /* String */

2026-04-29T06:02:06Z

String

← Nächstältere Version		Version vom 29. April 2026, 06:02 Uhr
Zeile 45:		Zeile 45:
	=== String ===		=== String ===

	If the pin's datatype is <CODE>String</code>, then no leading/trailing quotes are needed		If the pin's datatype is <CODE>String</code>, then no leading/trailing single quotes are needed.
	~~(actually:~~ if there are quotes, these will be part of the string). <br>However, '''quotes are needed''' if the type is not unambiguously a String type (i.e. Any or a Union type).		In fact, if there are quotes, these will be part of the string. <br>However, '''quotes are needed''' if the type is not unambiguously a String type (i.e. Any or a Union type).

	By default, NO C-style escape sequences are interpreted - i.e. the string is taken "as-is".		By default, NO C-style escape sequences are interpreted - i.e. the string is taken "as-is".
	<br>If you want or need ~~those~~, either enable the "''C-Escapes''" toggle via the freeze-value's popup menu, or freeze it as "C-String", which is a pseudo datatype offered in the freeze as menu.		<br>If you want or need control or non-latin1 characters, either enable the "''C-Escapes''" toggle via the freeze-value's popup menu, or freeze it as "C-String", which is a pseudo datatype offered in the freeze as menu.

	You can then use the escapes:		You can then use the escapes:

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

2026-04-29T05:59:21Z

$(...) Expansion

← Nächstältere Version		Version vom 29. April 2026, 05:59 Uhr
Zeile 114:		Zeile 114:
	=== $(...) Expansion ===		=== $(...) Expansion ===
	In addition to the visible environment variables, the following builtin names are allowed:		In addition to the visible environment variables, the following builtin names are allowed:
	* AttachmentsDirectory - the directory, where all attachments of the suite are located.		* <code>AttachmentsDirectory</code> - the directory, where all attachments of the suite are located.
	* Attachments - the same, but a little shorter		* <code>Attachments</code> - the same, but a little shorter
	* ExecutionDirectory - a temporary directory, which vanishes after the execution		* <code>ExecutionDirectory</code> - a temporary directory, which vanishes after the execution
	* ExpeccoInstallationDirectory - the directory, where expecco was installed		* <code>ExpeccoInstallationDirectory</code> - the directory, where expecco was installed
	* ExpeccoLibraryDirectory - the directory, where the libraries delivered with expecco live (first supported in 23.1)		* <code>ExpeccoLibraryDirectory</code> - the directory, where the libraries delivered with expecco live (first supported in 23.1)
	* ExpeccoPluginDirectory - the directory, where expecco's plugins are installed		* <code>ExpeccoPluginDirectory</code> - the directory, where expecco's plugins are installed
	* ProjectDirectory - the temporary project directory		* <code>ProjectDirectory</code> - the temporary project directory
	* HomeDirectory - the user's home directory		* <code>HomeDirectory</code> - the user's home directory
	* TmpDirectory - a temporary directory (subfolder of the system's tmp directory)		* <code>TmpDirectory</code> - a temporary directory (subfolder of the system's tmp directory)
	* CurrentDirectory - the "current" directory (see below)		* <code>CurrentDirectory</code> - the "current" directory (see below)
	* DocumentsDirectory - the "documents" directory		* <code>DocumentsDirectory</code> - the "documents" directory
	* DesktopDirectory - the "desktop" directory		* <code>DesktopDirectory</code> - the "desktop" directory
	* LoginName - your login name (username under Unix/Linux/OSX)		* <code>LoginName</code> - your login name (username under Unix/Linux/OSX)
	* UserName - your full name (if known, otherwise the login name)		* <code>UserName</code> - 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: /* $(...) Expansion */

2026-04-29T05:56:54Z

$(...) Expansion

← Nächstältere Version		Version vom 29. April 2026, 05:56 Uhr
Zeile 131:		Zeile 131:
	* <''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

	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.

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

Cg: /* Geometric Objects (Points and Rectangles) */

2026-04-29T05:55:34Z

Geometric Objects (Points and Rectangles)

← Nächstältere Version		Version vom 29. April 2026, 05:55 Uhr
Zeile 90:		Zeile 90:
	Points are entered (in Smalltalk syntax) as:		Points are entered (in Smalltalk syntax) as:
	* <code>''x'' @ ''y''</code>		* <code>''x'' @ ''y''</code>
	* <code>Point x:''x&'' y:''y''</code>		* <code>Point x:''x'' y:''y''</code>
	where ''x&'' and ''y'' are numeric constants (typically integers).		where ''x&'' and ''y'' are numeric constants (typically integers).

Cg: /* Geometric Objects (Points and Rectangles) */

2026-04-29T05:55:06Z

Geometric Objects (Points and Rectangles)

← Nächstältere Version		Version vom 29. April 2026, 05:55 Uhr
Zeile 89:		Zeile 89:
	=== Geometric Objects (Points and Rectangles) ===		=== Geometric Objects (Points and Rectangles) ===
	Points are entered (in Smalltalk syntax) as:		Points are entered (in Smalltalk syntax) as:
	* <code>~~<~~x~~>~~ @ ~~<~~y~~>~~</code>		* <code>''x'' @ ''y''</code>
	* <code>Point x:~~<~~x&~~gt;~~ y:~~<~~y~~>~~</code>		* <code>Point x:''x&'' y:''y''</code>
	where ~~<~~x&~~gt;~~ and ~~<~~y~~>~~ are numeric constants (typically integers).		where ''x&'' and ''y'' are numeric constants (typically integers).

	Rectangles (in Smalltalk syntax):		Rectangles (in Smalltalk syntax):
	* <code>(~~<~~xL~~>~~ @ ~~<~~yT~~>~~) extent:(~~<~~w~~>~~ @ ~~<~~h~~>~~)</code>		* <code>(''xL'' @ ''yT'') extent:(''w'' @ ''h'')</code>
	* <code>(~~<~~xL~~>~~ @ ~~<~~yT~~>~~) corner:(~~<~~xR~~>~~ @ ~~<~~yB~~>~~)</code>		* <code>(''xL'' @ ''yT'') corner:(''xR'' @ ''yB'')</code>
	* <code>Rectangle left:~~<~~xL~~>~~ top:~~<~~yT~~>~~ width:~~<~~wT~~>~~ height:~~<~~hT~~>~~</code>		* <code>Rectangle left:''xL'' top:''yT'' width:''wT'' height:''hT''</code>
	* <code>Rectangle left:~~<~~xL~~>~~ top:~~<~~yT~~>~~ right:~~<~~xR~~>~~ bottom:~~<~~yB~~>~~</code>		* <code>Rectangle left:''xL'' top:''yT'' right:''xR'' bottom:''yB''</code>
	where ~~<~~xL~~>~~ and ~~<yT>~~ are the left and top coordinates, ~~<~~xR~~>~~ and ~~<~~yB~~>~~ are the coordinates of the corner (the first pixel outside the rectangle), and ~~<~~w~~>~~ and ~~<~~h~~>~~ are the extent (width and height) of the rectangle.		where ''xL'' and ''y'' are the left and top coordinates, ''xR'' and ''yB'' are the coordinates of the corner (the first pixel outside the rectangle), and ''w'' and ''h'' are the extent (width and height) of the rectangle.

	=== Any ===		=== Any ===