Quote:
Originally Posted by Todd
If the High priority task, when it goes to set the bits notices that they haven't been flipped back, then it knows that the low priority task has not run in that timeframe.
Once it realizes that a certain number of frames have passed without the other task 'reporting in', it knows something is wrong.
|
I like that approach Todd.
Has anybody else used this or something similar, and if so, did it prove helpful?