Quote Originally Posted by dday9 View Post
Take a look at JMcIlhinney's thread on adding a pause to your code, if used properly you can do exactly what you're wanting to do:
Code:
Run task 1
Pause -x- time
Run task 2
Pause -y- time
Run task 3
Pause -z- time
etc.
The way that he structured the code, doesn't block the UI and it doesn't use a 'busy wait', which by the way Thread.Sleep will block the UI.
Thank you for the link. Not sure how to "trigger" the start of the ITask object.
Quote Originally Posted by Niya View Post
I think a very important question needs to be answered first: Do you want these ITask implementers to be able to start themselves ? Or do you intend to have a collection based object that takes ITask objects and start them when its their time ?
I think it would be better if I created a TaskHandler class that handled the collection of ITask objects and would start/stop them appropriately. I think the TaskHandler class should also "paint"/display the current schedule to the user

Is there a control that would be well suited for a scheduling type thing?