configuration variables are now provided to the receivers right away without any read(). Updates will never be sent.

allow obtaining the config values already before connections have been made through a speicial get() function

fixed connectTo() so it now uses the dynamic/virtual model and thus obeys e.g. eliminated hierarchies etc.

Fixed tests which were broken after updating the demoApp due to changed map files. Now the tests have their independent map files.

A DeviceModule now returns the same VariableNetworkNode when asked for the same register multiple times. This leads to a new restriction that registers can now only be either read or written. This restriction can be mitigated by using the logical name mapper to create an alias of the register. This has been implemented for the tests and the demo application.

- allow setting the "eliminateHierarchy" flag in the constructor of a module

This is an interface change which was done in an incompatible way!

- updated the tests for the testable mode and test the TestFacility class there as well

implement the "testable mode" in which the application can be paused and resumed by the test routine

Added a TestDecoratorRegisterAccessor which is optionally put around accessors to facilitate test of applications. This TestDecoratorRegisterAccessor does not yet do anything, functionality will be added in the next commits.

Rebased the ScalarAccessor and ArrayAccessor classes onto the mtca4u::NDRegisterAccessorBridge class.
Known problems present: code compiles but tests do not run

Removed the macros for defining accessors and introduced convenience classes instead. This adds slightly more syntactic sugar, but also allows more flexibility and seems to be a more coherent interface.

This commit incompatibly breaks the interface with the previous versions. Since ApplicationCore is not yet used in any productive environment, no compatibility is provided.

fixed a bug in the test: a module was defined at the same scope as the application, which lead to crashes when terminating the application sometimes
(same as last commit, but for a different test)

fixed a bug in the test: a module was defined at the same scope as the application, which lead to crashes when terminating the application sometimes

Added names and owners for modules, to build a full hierarchy chain. The syntax for creating modules is now not so nice, a better way has to be found (maybe by adding a macro if better solution can be found).

Read all application inputs once before starting the module threads, so the initial values are correctly present.

For this purpose, additional changes were necessary:
- Added support for constant values as feeders and consumers (just ignore the writes)
- Connect all unconnected application accessors to constants after defining the connections and before creating the implementations
- Renamed the user-overridden function "initialise()" into "defineConnections()", since more actions are now necessary during initialise().
- The connections are now made (i.e. the implementations are created) during the initialisation phase

allow specifying the array length for direct connections between device and control system (as the type is already defined in this case)

Added description field to the variables. It is currently ignored and will be added to the XML file in a next step.