In the old model, we had a signal per thread and a thread based valve Logic.
Now, it is moved to CO/COT
So if RateControl sets "rate" it is done by his own private member m_pRateSlider which carry the valve logic.
BpmControl has an other private m_pRateSlider with its own valve logic.
So BpmControll will receive all updates from RateControl, (unless there is no bug ;-))
So we have now the benefit that two objects in the same thread can communicate via COs by a common interface :-))
Great!
Ah, I think I have got the point!
In the old model, we had a signal per thread and a thread based valve Logic.
Now, it is moved to CO/COT
So if RateControl sets "rate" it is done by his own private member m_pRateSlider which carry the valve logic.
BpmControl has an other private m_pRateSlider with its own valve logic.
So BpmControll will receive all updates from RateControl, (unless there is no bug ;-))
So we have now the benefit that two objects in the same thread can communicate via COs by a common interface :-))
Great!