Well, I was planning to use XInput as device independent interface for
WinTab API implementation (which is non-Microsoft API) . Though, I thought
that joystick driver also may be implemented this way. That's why I wanted
to make this layer API-independent. Basically, it supposed to provide a
little bit more convinient way to enumerate available devices, open/close
specific device and simplifies event processing. It also must cover
interaction with X11DRV, so windows driver (WinTab/Joystick/etc) will see
HWNDs instead of Window*, some simplified variants of XEvent structures (I
guess, normal KeyEvent, MotionNotify, etc handlers can give a clue what we
actually need from XEvent). So, it's EnumDevices, OpenDevice, CloseDevice,
and SelectEvent functions, plus definition for API-specific callback
function to handle events. Wrappers for other XInput functions can be
implemented on 'as-needed' basis.
As for mouse emulation. We don't actually need this, because XFree86
implementation supports a non standard feature called AlwaysCore which
enables an XInput device to send both core and extended events at the same
time. I guess, some advanced mouse driver may be implemented as XInput
extension to allow access to new features (mouse wheel?, extra buttons,
etc). So, probably, we also can get some extra events for core devices via
XInput.
--
Serge Ivanov
[EMAIL PROTECTED]
Ove Kaaven wrote in message ...
>
>On Tue, 12 Sep 2000, Serge Ivanov wrote:
>
>> I'm working on WinTab (industrial standard API for graphic tablets)
support
>> under Wine. Quite an obvious and probably the only way to do it, is to
use
>> XInput extension.
>
>May I ask which Win32 API is supposed to access it? winmm? directinput?
>just plain user32 (emulating a mouse or something)? something I've
>forgotten? Because we've often thought of adding XInput support to e.g.
>winmm, so the joystick driver can use it, for example... and we want
>DirectInput to use winmm's drivers eventually...
>
--
The address in the headers is not the poster's real email address. Do not send
private mail to the poster using your mailer's "reply" feature. CC's of mail
to mailing lists are OK. Problem reports to "[EMAIL PROTECTED]".
The poster's email address is "[EMAIL PROTECTED]".
