Using tasks in VEXcode

[weilin]

Since, I don’t know what are your goals, I’ll just provide links to several very helpful replies by jpearman about tasks, that I had bookmarked:

Understanding Competition Methods & Template

I’m just going to throw this code up. It demonstrates a couple of things, how to start and stop tasks, how to monitor competition control to perform actions when the robot goes in and out of enabled. Ask questions as necessary. #include "robot-config.h" /*----------------------------------------------------------------------------*/ /* */ /* Module: main.cpp */ …

Vex::task scope

Not as such at the moment. Individual tasks can be stopped, if you created a task like this. task mytask( mycallback ); That task can be stopped by using mytask.stop(); but there are other ways as well, it can be stopped by using the name of the callback. task::stop( mycallback ); or the task instance task::stop( mytask ); tasks behave much as ROBOTC tasks did, students have all sort of bad usage patterns, treating them like functions etc. so, for example, constantly creating a task in …

Vex::task scope

just FYI, todays update of VEXcode now has a “stop all tasks” class member function for task and thread. task::stopAll(); or thread::interruptAll(); main will not be stopped, events will not be unregistered. motors will continue to run if field control still has the robot enabled.

Help with Task Programming

The VCS/VEXcode scheduler is very similar to the ROBOTC scheduler. There are some differences due to the fact that ROBOTC was running as a virtual machine and had more control over when exactly the task switching could occur, however, the concepts are very similar. startTask( myTask ) becomes vex::task taskId( myTask ) wait1Msec(10) becomes task::sleep(10) AbortTimeSlice() becomes task::yield() and so on. (and I fixed the broken links in the original topic)