http://bugs.winehq.org/show_bug.cgi?id=18424
--- Comment #61 from Jonas Maebe jonas.bugzilla@gmail.com 2011-06-25 05:51:52 CDT --- (In reply to comment #60)
Yes I had noticed the 1.3.23 has been released with the patch. :) I haven't tried it yet, but running the 1.3.18 version I did get the following fixmes:
fixme:dinput:SysMouseWImpl_Acquire Clipping cursor to (0,0)-(1920,1080) fixme:dinput:get_osx_device_elements Unhandled type 257 fixme:dinput:get_osx_device_elements Unhandled type 257 fixme:dinput:get_osx_device_elements Unhandled type 257 fixme:dinput:get_osx_device_elements Unhandled type 257 fixme:dinput:get_osx_device_elements Unhandled type 257 fixme:wave:wodDsCreate DirectSound not implemented fixme:wave:wodDsCreate The (slower) DirectSound HEL mode will be used instead. fixme:wave:AudioUnit_SetVolume independent left/right volume not implemented (1.000000, 1.000000) fixme:wave:wodDsCreate DirectSound not implemented fixme:wave:wodDsCreate The (slower) DirectSound HEL mode will be used instead.
The middle ones are to do with get_osx_device_elements ... any idea what that is about?
Yes, I also get them (and some others) for the PS3 controller. You can probably ignore them. Those controller element types correspond to kIOHIDElementTypeFeature, which according to Apple means "Describes input and output elements not intended for consumption by the end user".
I don't know who is supposed to consume them instead (or even who/what the "end user" is in this context) nor what they mean, but they definitely do not correspond to buttons, hat switches, axes, force feedback (which isn't supported yet in the OS X code either, fwiw), and the like.
It's possible that they could nevertheless be passed on to DirectInput in a meaningful way, but I don't know how since I don't know what they mean.