On Thu, Apr 25, 2013 at 1:29 AM, Todd Showalter <t...@electronjump.com>wrote:
> On Wed, Apr 24, 2013 at 5:03 PM, Rick Yorgason <r...@firefang.com> wrote: > > > One thing I would expect a joystick abstraction to do that I don't > expect a > > mouse abstraction to do is, if I plug two mice into a system I expect > them > > both to control the same cursor, but with joysticks I always want to know > > which joystick is sending each message. > > Yes, definitely. Which also leads to the whole device naming > question; ie: if someone unplugs a controller and plugs it back in, > how do you make sure player 2 stays player 2? But I think as long as > the rules are simple (if one controller disappears and reappears, > assume it's the same player, if multiple controllers disappear and > reappear at the same time, well, pilot error, user gets whatever they > get), it's largely a problem that can be papered over. Although there doesn't seem to be unique identifiers in the devices. It is possible to identify a controller by using the USB port it was connected into, and the device class. You can use the same technique to identify an USB hub.
_______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel