CS_TBL, that's basically what I'd be doing. Actually, the initial event is not going to be posted by the function called by the event, but by another function.
Sticking with the names you provided, SomeFunction() needs to get called basically every frame for brief periods of time - but does not need to be called at all 95% of the time.
It seemed like posting an event, whose event handler calls the function - and then posting the event from within the function until the function is finished, is the most elegant way to handle the situation. Oh yeah, the other criteria is that the event itself (streaming large files into banks) could take a few seconds if I did it all at once, but instead I just stream a few hundred bytes and then post the event and exit the function so that the rest of my main loop can execute.
Maybe there's a much better way to do this?
Sticking with the names you provided, SomeFunction() needs to get called basically every frame for brief periods of time - but does not need to be called at all 95% of the time.
It seemed like posting an event, whose event handler calls the function - and then posting the event from within the function until the function is finished, is the most elegant way to handle the situation. Oh yeah, the other criteria is that the event itself (streaming large files into banks) could take a few seconds if I did it all at once, but instead I just stream a few hundred bytes and then post the event and exit the function so that the rest of my main loop can execute.
Maybe there's a much better way to do this?