[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] appl_getinfo documentation bug?



hello,

On Fri, 1 Oct 2004 17:00:00 +0200, Gerhard Stoll <Gerhard_Stoll@b.maus.de> wrote:

AB> What's the definition of each bit in ap_gout3 ?

It it a bit vector for each wheel the mouse have. So the programmer knows what
value in ev_hwlpbuff is correct.

I see...

IMHO, the XaAES convention is better: 0=no moose wheel support in the AES, 1=the AES extends some functions with mouse wheel data.

appl_getinfo should give informations regarding the AES (is the AES support this or this feature?). appl_getinfo is not the right place to get information about the device itself.

If an application wants to know if the mouse has 0, 1, 2 or more wheels, and 1,2,3... bouttons, then the application have to ask this to the mouse driver.

So, i would vote for keeping the XaAES convention (out3=1 because XaAES support mouse wheel in its functions).

Any comment ?

best regards,
Arnaud.