DiagramElements-Connection/en - Versionsgeschichte

Cg: /* Guidelines for Pin-Type Declarations */

2021-12-06T09:46:46Z

Guidelines for Pin-Type Declarations

← Nächstältere Version		Version vom 6. Dezember 2021, 09:46 Uhr
Zeile 37:		Zeile 37:
	In general, avoid "Any"-typed outputs (see "[[Any_Type_Considered_Harmful]]").		In general, avoid "Any"-typed outputs (see "[[Any_Type_Considered_Harmful]]").

			==See also==
	~~See also:~~ [[DiagramElements-Pin/en \| Pin]]		[[DiagramElements-Pin/en \| Pin]] [[DiagramElements-Step/en \| Step]]

	[[Category: Diagram Elements]]		[[Category: Diagram Elements]]

Cg: /* Controlling the Connections Look */

2021-12-06T01:58:03Z

Controlling the Connections Look

← Nächstältere Version		Version vom 6. Dezember 2021, 01:58 Uhr
Zeile 21:		Zeile 21:
	:- if it is connected to another pin, then a connection to the same output will be created.		:- if it is connected to another pin, then a connection to the same output will be created.

	=== Controlling ~~the~~ ~~Connections~~ Look ===		=== Controlling a Connection's Look ===
	Click on a connection to select it and choose an appropriate item from the right-button menu.		Click on a connection to select it and choose an appropriate item from the right-button menu.

Cg: /* Suppressing the Type Check */

2021-12-06T01:57:38Z

Suppressing the Type Check

← Nächstältere Version		Version vom 6. Dezember 2021, 01:57 Uhr
Zeile 21:		Zeile 21:
	:- if it is connected to another pin, then a connection to the same output will be created.		:- if it is connected to another pin, then a connection to the same output will be created.

			=== Controlling the Connections Look ===
			Click on a connection to select it and choose an appropriate item from the right-button menu.

			The toolbar also contains buttons for frequently needed operations on connections, and to change the defaults for future connections.

	=== Suppressing the Type Check ===		=== Suppressing the Type Check ===
	In some situations, expecco considers pins incompatible, although in reality they are not. This happens, when an output has been over-generalized (for example as "Any" or "Number") and needs to be connected to a less general input pin (for example "String" or "Integer").		In some situations, expecco considers pins incompatible, although in reality they are not. This happens, when an output has been over-generalized (for example as "Any" or "Number") and needs to be connected to a less general input pin (for example "String" or "Integer").

Cg: /* Introduction */

2021-12-06T01:55:52Z

Introduction

← Nächstältere Version		Version vom 6. Dezember 2021, 01:55 Uhr
Zeile 3:		Zeile 3:
	A connection is used to interconnect two [[DiagramElements-Pin\|pins]] in an activity diagram. Depending on the type of the pins, the connection models either a data flow- or a control flow-connection.		A connection is used to interconnect two [[DiagramElements-Pin\|pins]] in an activity diagram. Depending on the type of the pins, the connection models either a data flow- or a control flow-connection.

	[[Datei:Connection1.png\|mini]]		[[Datei:Connection1.png\|mini\|Connection between Steps]]

	[[Datei:Connection2.png\|mini]]		[[Datei:Connection2.png\|mini\|Connection from Action's Input to a Step]]

	[[Datei:Connection3.png\|mini]]		[[Datei:Connection3.png\|mini\|Connection from a Step to an Action's Output]]

	[[Datei:Connection4.png\|mini]]		[[Datei:Connection4.png\|mini\|A Hidden Connection]]

	[[Datei:Connection5.png\|mini]]		[[Datei:Connection5.png\|mini\|A Hidden Connection when Mouse is Over]]

	[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] <sup>(1)</sup> and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.		[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] <sup>(1)</sup> and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.

Cg: /* Introduction */

2021-12-06T01:51:47Z

Introduction

← Nächstältere Version		Version vom 6. Dezember 2021, 01:51 Uhr
Zeile 4:		Zeile 4:

	[[Datei:Connection1.png\|mini]]		[[Datei:Connection1.png\|mini]]

			[[Datei:Connection2.png\|mini]]

			[[Datei:Connection3.png\|mini]]

			[[Datei:Connection4.png\|mini]]

			[[Datei:Connection5.png\|mini]]

	[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] <sup>(1)</sup> and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.		[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] <sup>(1)</sup> and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.

Cg: /* Introduction */

2021-12-06T01:49:33Z

Introduction

← Nächstältere Version		Version vom 6. Dezember 2021, 01:49 Uhr
Zeile 2:		Zeile 2:

	A connection is used to interconnect two [[DiagramElements-Pin\|pins]] in an activity diagram. Depending on the type of the pins, the connection models either a data flow- or a control flow-connection.		A connection is used to interconnect two [[DiagramElements-Pin\|pins]] in an activity diagram. Depending on the type of the pins, the connection models either a data flow- or a control flow-connection.

			[[Datei:Connection1.png\|mini]]

	[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] <sup>(1)</sup> and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.		[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] <sup>(1)</sup> and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.

Cg: /* Introduction */

2021-12-06T01:32:12Z

Introduction

← Nächstältere Version		Version vom 6. Dezember 2021, 01:32 Uhr
Zeile 7:		Zeile 7:
	Outputs can be connected to multiple input pins, but each individual connection consists of exactly one input and one output pin. If an output pin has more than one connection, an outgoing value is sent to all connected inputs (concrete: a reference to the same datum-object is sent to all inputs). Thus, you should be careful with data object which contain state, and are mutated (modified) by an action. If that is the case, you should ensure proper synchronization to avoid time/execution order dependencies during execution (e.g. with control flow connections between trigger-in/trigger-out pins).		Outputs can be connected to multiple input pins, but each individual connection consists of exactly one input and one output pin. If an output pin has more than one connection, an outgoing value is sent to all connected inputs (concrete: a reference to the same datum-object is sent to all inputs). Thus, you should be careful with data object which contain state, and are mutated (modified) by an action. If that is the case, you should ensure proper synchronization to avoid time/execution order dependencies during execution (e.g. with control flow connections between trigger-in/trigger-out pins).

	Notes:<br><sup>1)</sup> For your convenience, the diagram editor will let you drag connections between two inputs:<br>- if the first input is frozen to a constant value or a variable. Then, the target input will be frozen to the same value or variable.<br>- if it is connected to another pin, then a connection to the same output will be created.		Notes:<br><sup>1)</sup> For your convenience, the diagram editor will let you drag connections between two inputs:
			:- if the first input is frozen to a constant value or a variable. Then, the target input will be frozen to the same value or variable.
			:- if it is connected to another pin, then a connection to the same output will be created.

	=== Suppressing the Type Check ===		=== Suppressing the Type Check ===

Cg: /* Introduction */

2021-12-06T01:31:30Z

Introduction

← Nächstältere Version		Version vom 6. Dezember 2021, 01:31 Uhr
Zeile 3:		Zeile 3:
	A connection is used to interconnect two [[DiagramElements-Pin\|pins]] in an activity diagram. Depending on the type of the pins, the connection models either a data flow- or a control flow-connection.		A connection is used to interconnect two [[DiagramElements-Pin\|pins]] in an activity diagram. Depending on the type of the pins, the connection models either a data flow- or a control flow-connection.

	[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] (~~[[#NOTE1\|~~1]]) and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.		[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] <sup>(1)</sup> and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.

	Outputs can be connected to multiple input pins, but each individual connection consists of exactly one input and one output pin. If an output pin has more than one connection, an outgoing value is sent to all connected inputs (concrete: a reference to the same datum-object is sent to all inputs). Thus, you should be careful with data object which contain state, and are mutated (modified) by an action. If that is the case, you should ensure proper synchronization to avoid time/execution order dependencies during execution (e.g. with control flow connections between trigger-in/trigger-out pins).		Outputs can be connected to multiple input pins, but each individual connection consists of exactly one input and one output pin. If an output pin has more than one connection, an outgoing value is sent to all connected inputs (concrete: a reference to the same datum-object is sent to all inputs). Thus, you should be careful with data object which contain state, and are mutated (modified) by an action. If that is the case, you should ensure proper synchronization to avoid time/execution order dependencies during execution (e.g. with control flow connections between trigger-in/trigger-out pins).

	Notes:<br><dl>~~<dt>{{anchor\| NOTE1}}(~~1)</~~dt><dd~~>For your convenience, the diagram editor will let you ~~''connect''~~ two inputs, if the first input is frozen to a constant value or a variable. Then, the target input will be frozen to the same value or variable.<~~/dd></dl~~>		Notes:<br><sup>1)</sup> For your convenience, the diagram editor will let you drag connections between two inputs:<br>- if the first input is frozen to a constant value or a variable. Then, the target input will be frozen to the same value or variable.<br>- if it is connected to another pin, then a connection to the same output will be created.

	=== Suppressing the Type Check ===		=== Suppressing the Type Check ===
	In some situations, expecco considers pins incompatible, although in reality they are not. This happens, when an output has been over-generalized (for example as "Any" or "Number") and needs to be connected to a less general input pin (for example "String" or "Integer"). In such situations, expecco assumes that the output my generate values which cannot be consumed correctly by the input. However, expecco does not look into the actual code inside elementary blocks, and the code may actually only generate acceptable values.		In some situations, expecco considers pins incompatible, although in reality they are not. This happens, when an output has been over-generalized (for example as "Any" or "Number") and needs to be connected to a less general input pin (for example "String" or "Integer").

			In such situations, expecco assumes that the output may generate values which cannot be consumed correctly by the input. However, expecco does not look into the actual code inside elementary blocks, and the code may actually accept the value.
⚫	If you are sure, that only correct values will ~~actually~~ be generated at the output pin, you can enforce a connection (against expecco's resistance, if you like), by pressing the <KBD>CTRL</KBD>-key while dragging the connection in the editor. The editor will then create the connection, but draw it as a dotted line, to indicate a possible type conflict at execution time. This can be changed to a solid line via the "''Disable Type Check''" context menu item.

		⚫	If you are sure, that only correct values will be generated at the output pin, you can enforce a connection (against expecco's resistance, if you like), by pressing the <KBD>CTRL</KBD>-key while dragging the connection in the editor. The editor will then create the connection, but draw it as a dotted line, to indicate a possible type conflict at execution time. This can be changed to a solid line via the "''Disable Type Check''" context menu item.

	=== Guidelines for Pin-Type Declarations ===		=== Guidelines for Pin-Type Declarations ===
Zeile 18:		Zeile 20:
	In general, avoid "Any"-typed outputs (see "[[Any_Type_Considered_Harmful]]").		In general, avoid "Any"-typed outputs (see "[[Any_Type_Considered_Harmful]]").

			See also: [[DiagramElements-Pin/en \| Pin]]

	[[Category: Diagram Elements]]		[[Category: Diagram Elements]]

Cg: /* Introduction */

2019-10-12T15:34:42Z

Introduction

← Nächstältere Version		Version vom 12. Oktober 2019, 15:34 Uhr
Zeile 7:		Zeile 7:
	Outputs can be connected to multiple input pins, but each individual connection consists of exactly one input and one output pin. If an output pin has more than one connection, an outgoing value is sent to all connected inputs (concrete: a reference to the same datum-object is sent to all inputs). Thus, you should be careful with data object which contain state, and are mutated (modified) by an action. If that is the case, you should ensure proper synchronization to avoid time/execution order dependencies during execution (e.g. with control flow connections between trigger-in/trigger-out pins).		Outputs can be connected to multiple input pins, but each individual connection consists of exactly one input and one output pin. If an output pin has more than one connection, an outgoing value is sent to all connected inputs (concrete: a reference to the same datum-object is sent to all inputs). Thus, you should be careful with data object which contain state, and are mutated (modified) by an action. If that is the case, you should ensure proper synchronization to avoid time/execution order dependencies during execution (e.g. with control flow connections between trigger-in/trigger-out pins).

	Notes:<br><dl><dt>~~<html><a~~ ~~NAME="~~NOTE1~~"></html>~~(1)~~<html></a></html>~~</dt><dd>For your convenience, the diagram editor will let you ''connect'' two inputs, if the first input is frozen to a constant value or a variable. Then, the target input will be frozen to the same value or variable.</dd></dl>		Notes:<br><dl><dt>{{anchor\| NOTE1}}(1)</dt><dd>For your convenience, the diagram editor will let you ''connect'' two inputs, if the first input is frozen to a constant value or a variable. Then, the target input will be frozen to the same value or variable.</dd></dl>

	=== Suppressing the Type Check ===		=== Suppressing the Type Check ===

Cg: /* Introduction */

2019-10-12T15:30:48Z

Introduction

← Nächstältere Version		Version vom 12. Oktober 2019, 15:30 Uhr
Zeile 3:		Zeile 3:
	A connection is used to interconnect two [[DiagramElements-Pin\|pins]] in an activity diagram. Depending on the type of the pins, the connection models either a data flow- or a control flow-connection.		A connection is used to interconnect two [[DiagramElements-Pin\|pins]] in an activity diagram. Depending on the type of the pins, the connection models either a data flow- or a control flow-connection.

	[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] (~~<html><A REF="~~#NOTE1~~"></html>~~1~~<html></a></html>~~) and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.		[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] ([[#NOTE1\|1]]) and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.

	Outputs can be connected to multiple input pins, but each individual connection consists of exactly one input and one output pin. If an output pin has more than one connection, an outgoing value is sent to all connected inputs (concrete: a reference to the same datum-object is sent to all inputs). Thus, you should be careful with data object which contain state, and are mutated (modified) by an action. If that is the case, you should ensure proper synchronization to avoid time/execution order dependencies during execution (e.g. with control flow connections between trigger-in/trigger-out pins).		Outputs can be connected to multiple input pins, but each individual connection consists of exactly one input and one output pin. If an output pin has more than one connection, an outgoing value is sent to all connected inputs (concrete: a reference to the same datum-object is sent to all inputs). Thus, you should be careful with data object which contain state, and are mutated (modified) by an action. If that is the case, you should ensure proper synchronization to avoid time/execution order dependencies during execution (e.g. with control flow connections between trigger-in/trigger-out pins).

← Nächstältere Version		Version vom 6. Dezember 2021, 01:55 Uhr
Zeile 3:		Zeile 3:
	A connection is used to interconnect two [[DiagramElements-Pin\|pins]] in an activity diagram. Depending on the type of the pins, the connection models either a data flow- or a control flow-connection.		A connection is used to interconnect two [[DiagramElements-Pin\|pins]] in an activity diagram. Depending on the type of the pins, the connection models either a data flow- or a control flow-connection.

	[[Datei:Connection1.png\|mini]]		[[Datei:Connection1.png\|mini\|Connection between Steps]]

	[[Datei:Connection2.png\|mini]]		[[Datei:Connection2.png\|mini\|Connection from Action's Input to a Step]]

	[[Datei:Connection3.png\|mini]]		[[Datei:Connection3.png\|mini\|Connection from a Step to an Action's Output]]

	[[Datei:Connection4.png\|mini]]		[[Datei:Connection4.png\|mini\|A Hidden Connection]]

	[[Datei:Connection5.png\|mini]]		[[Datei:Connection5.png\|mini\|A Hidden Connection when Mouse is Over]]

	[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] <sup>(1)</sup> and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.		[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] <sup>(1)</sup> and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.

← Nächstältere Version		Version vom 6. Dezember 2021, 01:51 Uhr
Zeile 4:		Zeile 4:

	[[Datei:Connection1.png\|mini]]		[[Datei:Connection1.png\|mini]]

			[[Datei:Connection2.png\|mini]]

			[[Datei:Connection3.png\|mini]]

			[[Datei:Connection4.png\|mini]]

			[[Datei:Connection5.png\|mini]]

	[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] <sup>(1)</sup> and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.		[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] <sup>(1)</sup> and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.

← Nächstältere Version		Version vom 6. Dezember 2021, 01:49 Uhr
Zeile 2:		Zeile 2:

	A connection is used to interconnect two [[DiagramElements-Pin\|pins]] in an activity diagram. Depending on the type of the pins, the connection models either a data flow- or a control flow-connection.		A connection is used to interconnect two [[DiagramElements-Pin\|pins]] in an activity diagram. Depending on the type of the pins, the connection models either a data flow- or a control flow-connection.

			[[Datei:Connection1.png\|mini]]

	[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] <sup>(1)</sup> and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.		[[DiagramElements-Pin#Input Pin\|Input pins]] can only be connected with [[DiagramElements-Pin#Output Pin\|output pins]] <sup>(1)</sup> and the [[Datatype\|datatypes]] of the pins must be compatible. That means they either have the same type or the input pin has a "''more general''" type than the output pin;<br>e.g., for [[Datatype#Numeric Types\|numeric types]], Number is ''more general'' than both Integer or Float. Inputs with an [[Datatype#Any\|"Any" datatype]] are most general and can consume any value.