There has been quite a bit of discussion around issues associated with this scheduler, so I thought a separate thread was warranted.
See previous thread:
Specific issues were, what does
((u08 (*)(void)) romAdr)(); // call the task to initialize it
And trying to come up with a more bullet-proof debounce algorithm.