Re: [AD] 'None' mouse driver

[Chris <kcat@xxxxxxxxxx>]

What's the use in having a specific "none" mouse driver? AFAIK, the 
config option is to select a different driver for when the default one 
is behaving improperly. By allowing a NULL mouse driver, that would just 
invite more problems since as far as the programmer is concerned, 
install_mouse() returns 0 and it can be assumed there's a mouse. If a 
program needs the mouse it would quit if install_mouse failed, but if a 
stub driver is allowed there's no way to know if a mouse is present and 
useable or not.

However, perhaps it could be made that if the stub driver is selected, 
through either autodetection or user-specified in the config, 
install_mouse would return a failed value? That would alert the program 
that there's no useable mouse installed and to react accordingly.

Though wouldn't it be better if the stub mouse driver is called NONE, as 
opposed to an ambiguous 0?