Every robot needs a locky-thingy. A robot without one might fire when it isnāt supposed to, and hit the wrong target; e.g., a referee, FTA, or robot inspector.
Wouldnāt want that. Better put in the locky-thingy.
When I first read the title, I thought it said ādeceptive object nameā at which point it could be named āTHE_unlockā.
The locky-thing on our robot is called the trigger.
But since in this picture, the project is called DrawingPad, Iām assuming this isnāt for an FRC bot.
Itās actually a mutex, so it is supposed to lock data during reads and rights. Without properly using it, the software would crash spectacularly as the server is 100% threaded! Memory does not like to be read and written to at the same time, at the same location.
Use different memory: Instead of ROM (Read-Only Memory), use WOM (Write-Only memory). That will solve the problem completely.