There aren’t details on thread priority on api.vex.com. How does setPriority() actually work? Will messing with this cause stability issues? What does the priority number actually mean?
Additionally, why is the low thread priority variable name vex:
:threadPrioritylow not vex::threadPriorityLow?
That sounds like quite an old feature that wasn’t quite fully implemented, especially given that it doesnt follow the correct camelCase. It must be a spelling error for something that likely existed for a long period of time.
I might suggest ignoring that function and instead use mutexes to protect data that gets accessed between threads.
Higher priority tasks get priority over lower priority tasks if both need to run at the same time.
rarely used function on V5.
No particular reason, just what I called them back in 2018.
Sure it’s fully implemented.
These APIs were made to provide similar functionality to what we had with cortex and ROBOTC when the V5 was first introduced.