🚀 go-pugleaf

Bryce Nesbit listed a bunch of pinouts for controllers for the 
controller ports.

Is that all you are going to support with drivers in 1.4? I think a
more generic schieme should be used for the controller ports. 
Specificly, How would you handle a driving simulator which wanted
to use pins 1 and 3 as a reletive positioner (like 1 axis of the mouse)
for the stearing, pins 5 and 9 as absolute positioners (potentiometers)
for the gas and break respectivly, and pins 2 and 4 for fire buttons?
This doesn't fit any of the 5 controllers mentioned, but it is possible
that someone could want to build this or any of a whole slew of 
different controler designs.  I can see two solutions to this problem,
write a method of alocating the pins separately so that pins 1 and 3
can be alocated as a pair as a relative controler or separatly as 
buttons and so on for the output pins, and the pots. Or, you could
alocate the whole port and have all the possible inputs processed
simualtaniously. In this method if you had a button connected to pin 1
you would look at the button 1 bit of the button register, and if
there was a relitive controler attatched to pins 1 and 3 you would
look at the V count register (registers being elements in a ram based
structure in this context). Whatever is done, I would like to see
some built in software support for absolute positioners (analog
joystics) in version 1.4 of Workbench.