On 1/18/2017 1:26 PM, Evan Koblentz via vcf-midatlantic wrote:
Maybe. Perhaps there is another explanation: Consider whether when you press button 0- does LOGO give you ONE indication or is it as LONG as you hold it it gives you continuous "button pressed" indications?
I think just one (unrelated to programming a button press in push-to-talk mode, which is very easy and works great, but I wanted button 0 to work like turning the key in a car, not like a gas pedal.)
As for the sensor:
But it doesn't work because the program does not know which master to obey -- the joystick telling it to spin the steering motor or >the sensor telling it to stop! I tried some code saying if the sensor is true and the motor is true then turn off the port
You were on the right track for that, the joystick cannot command the motor if the sensor has triggered.
But it does. LOGO programs are iterative. It's constantly scanning to see if any input is happening. So you have the optical sensor being activated and telling the steering motor's port to turn off, while you also have the joystick pushed to one side telling the steering motor's port to turn on. That is why I figured some code that says "if both the joystick and the sensor are true, then turn the motor off" would help. But I couldn't get it to work. Dean and I tried a zillion syntax combinations with no luck. I'll look that up, seems you are saying logo lets you configure the response of the buttons as one-shot or continuous reporting of button pressed = true.