On 7/10/2018 1:06 PM, Bill Degnan via vcf-midatlantic wrote:
On Tue, Jul 10, 2018 at 12:49 PM Douglas Crawford via vcf-midatlantic < vcf-midatlantic@lists.vcfed.org> wrote:
If you are getting the same behavior from multiple joysticks, I'd fault the card or the code. (Unless of course these somehow aren't joysticks compatible with the card...)
The bits talked about here I assume are part of your logic, not the related to the stick command.
"But when I tried it on the Compaq, only two of the directions work correctly. It was something like left and forward; I forget exactly. One other direction turns on the wrong bits (1 and 4, same as its opposite direction, rather than 2 and 3 which it should be), even though I'm a million percent certain the code is right. Another direction works (bits 2 and 4) if I move the stick to its extreme edge, but while en route it turns on bit 3 for a second. That makes no sense! That's why I think the stick might be funky or somehow misadjusted even if it does work on the Apple side."
This sounds vaguely like the variable clobbering you had last year with the first lego code you were working on last year when you thought there was a bug in BASIC. Can you post the code?
Have you tried a simple test program for the joystick by itself to prove in fact the joystick is working right or not?
Having taught a class that included the differences in BASIC between different systems did they provide in their code samples a comparison chart of "if IBM do this" , "if Apple do that"? I assume you know and found all platform-centric code. I may have in my slide presentation a chart with common differences, but there are subtle little things. b
Its a good point. A review by someone who could spot such likely problem areas would be a good idea..