On Mon, Feb 20, 2017 at 3:43 PM, Evan Koblentz via vcf-midatlantic < vcf-midatlantic@lists.vintagecomputerfederation.org> wrote:
Also, this removes the *redundant* subroutine 3000 for the Forklift motor
All motors can be controlled in *one* subroutine at 2000 As you can see, the Poke value is the sum of M and F, So one setting doesn't disturb the other The new Input subroutine at 3000 takes care of *all* inputs and they're saved into their respective variables This allow non-blocking operation
Why do you have the POKEing routine (2000 series) transpire before it checks what the operate wants POKEd (3000 series)?
​subroutines can be arranged in any order​ as long as you Call them at the appropriate time Line 25 Calls Sub 3000 to check for any Input Line 30 Calls Sub 2000 to executes the commands given by the Input data Line 40 go do it again