Why does ProcessorMotion set the state of notified KF?
The ProcessorMotion::processCapture()
when a KF has been notified, its state is modified with the integrated state (L258 and L360 corresponding to RUNNING_WITH_KF_BEFORE_ORIGIN
and RUNNING_WITH_KF_AFTER_ORIGIN
). Why is that?
This KF may have been created by a processor that is able/not able to initialize its state.
- In the case that the processor that created the KF also initialized its state, I don't see a reason for which this initialization should be changed. It may be complemented with the missing keys if any...
- In the case that the processor that created the KF was not able to initialize its state, the state for this new KF is asked to
Problem
which asks the processors of typeIsMotion
(likeProcessorMotion
) to initialize it. So I don't see a reason why this state should be reset.
Also, in case of more than one ProcessorMotion
, the state will be reset more than once which is strange.. and the order in which the processors are called depends on the order of arrival of its correspondent captures so, it is undefined.