Heh - I’m sure this IS confusing!
The joystick is used to control a simulation of a Navy radar display called a 'Target Determination System". Bogies would show on the radar, and operators would move a cursor to the target in question. The
cursor is divided in to “C” shaped sections: One represents the actual bogie, and the other slow moving is the gun director. The gun is BIG and
takes a while to catch up to the actual bogie. When the two are closed, the operator presses the joystick, and that target is marked and
shot at and hopefully destroyed.
Since this is a ‘simulation’, the joystick may be pressed incorrectly so
there will be false presses. When Processing sees the two cursors being close enough, the target is outlined to indicate, and the director
cursor holds on it for about 10 seconds and then it is removed from the
screen - destroyed! It gets worse - The museum people would like to have a sound system play a loud BOOM when the target is destroyed - so even though the joystick initiates the target selection - Processing decides when it is actually on-target.
Next part of the fun is that I’m using an Arduino library “Joystick” that creates a real HID controller. So GameControlPlus can see it and Processing is reading it - but I have no other way to communicate with the Micro.