changed: deviceModule run is called before readLatest for comusming direction variables.
removed: impl->write() for NodeType::Device.

Test still does not work.
-Unable to get the exception status for the device throwing exception.
-Second device only works it has it's own trigger.

- removed debug output
- made implementation for not-fixed feeders (i.e. ApplicationModule feeders) of the trigger network identical to the implementation for fixed feeders

TriggerFanOut must catch exceptions when reading from the TransferGroup, since this cannot be handled by the decorator

Martin Killenberg authored 5 years ago and Martin Christoph Hierholzer committed 5 years ago

Creation of fanOuts is based on externalTriggerImpl (=trigger consumer), not externalTriggerNode (=trigger feeder).
- Fixes connection network but not exception handling.
- Lots of debug output left in the code for further investigation.

  DeviceModule and ControlSystemModule now do not take the optional prefix argument in their constructors any more. Use the [] operator instead to get the submodule.

- Add ExceptionHandlingDecorator and decorate all device variables with it.

- reformatted source code

Do not try to make consuming control system variables bidirectional. It was running into an assertion and anyway makes no sense.

do not create TestableModeAccessorDecorator for unidirectional PVs with both directions enabled (was hitting an assert)

- treat the two directions of bidirectional variables properly in testable mode (i.e. as individual variables with each one counter)
- fix a data race in testable mode in case a bidirectional variable rejected a value (was not holding a required lock)

fixed bidirectional direct application to control system connections (without any FanOut in between)

Fixed getCurrentVersionNumber() and setCurrentVersionNumber() so they always get/set the version number of the ApplicationModule and not e.g. of a VariableGroup.

- implement ThreadedFanOut version with return channel
- add test for ThreadedFanOut with return channel

bidirectional variables: pass on version numbers in modules from the last blocking read on to any write operations, to resolve conflicts of concurrent variable updates properly