Page History

...

Discussion/Conclusion: 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;

1. The Timezone issue has to be been re-adressed. According to Adrian it is not doing what we expectedThe .Net TimeZone does not provide what we need, while the TimeZoneInfo is only available in 3.5, and therefore will not run on MONO.
   Discussion/Conclusion led to the following decisions:
   1. Daylight Saving Time jumps in time series are not allowed
   2. The TimeSet will contain a property that expresses its offset from UTC, expressed in hours (see below). The Gui will check these offsets, and if they are different, it will ask the user to put a decorator in between.

1. Decorator issues:
   • Do we need to recognize the type of decorator (time, space, SI-conversion)?
   • Do we want to support 3th-party decorators indeed?
     Discussion/Conclusion: We will add an Update() method to the OutputDecorator. The linkable component calls this Update() on all its decorators at the end of its own Update(). This actually is completely the same as what happens in the current 1.4 Wrapper: after IEngine.PerformTimeStep the wrapper updates the buffers.

...