Possible changes to CommandableFragmentGenerator methods and sample child classes
As part of the ICARUS/artdaq discussion on 09-Feb-2016 (https://cdcvs.fnal.gov/redmine/projects/artdaq/wiki/February_9_2016_discussion_notes), the following issue were noted:
- Do we want to make more of the protected methods in CommandableFragmentGenerator virtual? [start, stop, report?] [also see notes on slide 8 of the Google slides from 09-Feb]
- The samples that we provide in the demo should have all of the methods that we want users to consider included, even if they are empty. We should also include comments that talk about what can be done in each of them, etc. Also include relative path to CommandableFragGen so users can easily look at.
#2 Updated by Kurt Biery over 4 years ago
- Status changed from New to Resolved
start, stop, and stopNoMutex were made pure virtual, and child classes were updated appropriately.
pause, pauseNoMutex, resume, report, and reportSpecific were updated to print out a compiler message when the default (empty) implementation is no over-ridden.
These changes implement the scheme that we decided upon in our internal discussions.