pic: Totally Desctiptive Object Name
 

Re: pic: Totally Desctiptive Object Name
 

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.

Re: pic: Totally Desctiptive Object Name
 

When I first read the title, I thought it said 'deceptive object name' at which point it could be named "THE_unlock".

Re: pic: Totally Desctiptive Object Name
 

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.

Re: pic: Totally Desctiptive Object Name
 

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.

Re: pic: Totally Desctiptive Object Name
 

Use different memory: Instead of ROM (Read-Only Memory), use WOM (Write-Only memory). That will solve the problem completely.