Conference 7.286::atarist

310.0. "Mouse/joystick interaction" by MINDER::GILBERT (North UK Region Appl'n Centre @MCO) Mon Nov 21 1988 07:40

    Here's a feature that kept me busy for a while:-
    
    Symptoms: the mouse moves the pointer around OK, but selecting is
    very strange - clicks are ignored, occur in bursts, or select
    the wrong item. Basically it looked like a faulty mouse button or
    logic associated with the mouseterface.
    
    I'd just about decided to take the rodent to a vet when as a last
    resort I unplugged everything down to just mouse and screen - problem
    went away!
    
    Anyway, to cut my enthralling saga short, the problem was the joystick
    - the autofire switch was on. This appears to load up something in the
    system and cause mouse button events to be reported late and in
    bursts.
    
    Just thought you might be interested...
    
    Rgds, Brian

The mouse button and the joystick fire button are the same thing.  They
are connected in parallel.

    My understanding is that the mouse port can also be a joystick port,
    so fire = mousekey sounds reasonable *for that port*. In my set-up
    the mouse and joystick are on separate ports. Surely the fire signals
    aren't commoned across the two ports? That would make it impossible
    to connect two joysticks!

	Pushing the port 1 joystick button is the same as pushing the
RIGHT mouse button on port 0.

    The poor little 6301 keyboard processor was probably bogged down
    handling button press events.
    
    						-Dave

    Thnaks for the input guys, explanation accepted. Degas Elite flips
    between menu and picture using the fire button.
    
    I would expect to find this documented in ST Intenals (Abacus),
    but it ain't!
    
    Rgds, Brian