Draft: Example of 'binding' tools to conditions and/or event data and/or other tools
Example for using conditions, event data and tools inside the implementation of a tool without 'polluting' the interface with extra arguments which ought to remain implementation details.
- factor out all conditions / event data / tools from MCReconstructible, and move it into a 'bound' tool
- modernize MCTrackGeomCriteria so that (eventually)
MCReconstructible will no longer need an
initialize
function
Edited by Andre Gunther
Merge request reports
Activity
Filter activity
added 1 commit
- 0e9708c4 - Playground for 'binding' tools to conditions and/or event data
- Resolved by Gerhard Raven
added 1 commit
- 10a438cc - make IMCReconstructible inherit from INamedInterface instead of IAlgTool
added 1 commit
- 3bdc875e - Allow both condition and event data to be bound
added 17 commits
-
3bdc875e...8c06dda7 - 11 commits from branch
master
- bad97f2d - Playground for 'binding' tools to conditions and/or event data
- c358b16f - WIP
- ff8a50d3 - make IMCReconstructible inherit from INamedInterface instead of IAlgTool
- 16e4b9a7 - replace initialize with property callback
- c8d6e31e - add generic handle mixin
- 675ce6dd - Allow both condition and event data to be bound
Toggle commit list-
3bdc875e...8c06dda7 - 11 commits from branch
Please register or sign in to reply