- Oct 15, 2024
-
-
vaeng authored
Closes #379
-
- Oct 14, 2024
-
-
Martin Christoph Hierholzer authored
If the return channel of a FeedingFanOut was removed because it is connected to the control system but not mapped there, the _returnSlave is not set and hence all read operations on it were crashing.
-
Martin Christoph Hierholzer authored
-
Martin Killenberg authored
fix(project-template): find pattern in coding style check
-
Martin Killenberg authored
-
Martin Killenberg authored
-
- Oct 11, 2024
-
-
Martin Christoph Hierholzer authored
-
- Oct 08, 2024
-
-
vaeng authored
-
- Oct 07, 2024
-
-
Martin Christoph Hierholzer authored
-
- Oct 04, 2024
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
We were holding an std::vector of an incomplete type (VariableNetworkNode) in a struct (ProcessVariableProperties), which is not allowed. This fix changes it into an std::vector of shared_ptrs. Since we are exposing this vector via ProcessVariableProxy::getNodes(), this presents a breaking API change. Since this is used mostly internally, this should not break much.
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
-
Martin Christoph Hierholzer authored
-
- Oct 01, 2024
-
-
Jens Georg authored
Fixes #8357
-
- Sep 27, 2024
-
-
- Sep 24, 2024
-
-
Jens Georg authored
-
Jens Georg authored
Fixes #7879
-
vaeng authored
-
- Sep 18, 2024
-
-
vaeng authored
-
- Sep 02, 2024
-
-
Martin Christoph Hierholzer authored
-
- Aug 30, 2024
-
-
Martin Christoph Hierholzer authored
This helps in two ways: 1. Doxygen is confused if there are multiple class defintions with the same name, which happens frequently in tests, e.g. "ModuleA" 2. Doxygen shows rather prominently all classes defined in the tests when viewing the Class List, while the important classes are "hidden" at first below the ChimeraTK namespace.
-
- Aug 28, 2024
-
-
Martin Christoph Hierholzer authored
update project template
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
- Aug 27, 2024
-
-
Martin Christoph Hierholzer authored
-
- Aug 26, 2024
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
The fix in the DeviceManager is more like a work-around for a false positive of gcc 13.
-
- Aug 13, 2024
-
-
Martin Killenberg authored
-
* most useful with StatusOutputs, where automatic propagation of 'data invalid' status is often not wanted * Change default behavior of StatusOutput and StatusWithMessage. By default, they no longer propagate DataValidity=invalid of owning module. They still propage DataValidity=invalid of explicitly set for the output. * Adapt test of DataValidity propagation for StatusOutput * Adapt test of StatusMonitor to new StatusOutput behaviour
-
"!sometag" is a negated tag which annihilates with "sometag" negated tags can be added like normal tags, and are used to remove their counterparts
-
- Aug 08, 2024
-
-
Martin Killenberg authored
-