...
Code Block | ||||
---|---|---|---|---|
| ||||
values = providingOutputItem.GetValues(consumerThatIsAsking); |
...
- Should we introduce a boolean argument that indicates whether the component should run in a pull mode (like in OpenMI 1.4) or in loop mode
?
Discussion/Conclusion part 2:
We decided to let the LinkableComponent have a propery: CascadingCallsDisabled.
The default is false, indicating that the component is running in Pull Driven mode (there will be a cascade of update() calls. This Pull Driven mode has to be supported by every component.
If set to true, the component is expected to run Update()-step by Update-Step(), controlled by some outer world (which may be another component). If the component does not support this Update() by Update() way of running, it will throw an Exception when CascadingCallsDisabled = true is called;
...
- We will introduce a boolean argument that indicates whether the component should run in a pull mode (like in OpenMI 1.4) or in loop mode
: Discuss component operation mode here - comment from Peter Gijsbers need to be discussed
- "string Validate()" / "bool IsValid(IExchangeItem item)" / "IsAvailable()", etc.
to be reviewed at this meeting
- When we get loops in the compositions - we have to tell which component will be first! In the new GUI, we will let the user indicate the 'Start up component'.
...