Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Joystick enumeration depends on connection order #40

Closed
matlo opened this issue Nov 27, 2013 · 5 comments
Closed

Joystick enumeration depends on connection order #40

matlo opened this issue Nov 27, 2013 · 5 comments

Comments

@matlo
Copy link
Owner

matlo commented Nov 27, 2013

From mathieu....@gmail.com on February 23, 2011 11:05:26

In the config files for emuclient, only the id is used to identify the joystick, which is a big issue because the id only depends on the connection order.

Consider we have two different joysticks (not the same model) 'A' and 'B', and a PC with no currently plugged joystick. If 'A' is plugged first and 'B' is plugged second, then 'A' will have 0 as id, and 'B' will have '1' as id. If 'B' is plugged first and 'A' is plugged second, then 'A' will have 1 as id, and 'B' will have '0' as id.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=38

@matlo
Copy link
Owner Author

matlo commented Nov 27, 2013

From mathieu....@gmail.com on February 23, 2011 02:05:38

The clean way to do is to map the id to a virtual id.

Ex:

js1 = type A, id 1 => vid = 1
js2 = type B, id 2 => vid = 1
js3 = type A, id 3 => vid = 2
js3 = type C, id 4 => vid = 1
js4 = type B, id 5 => vid = 2

@matlo
Copy link
Owner Author

matlo commented Nov 27, 2013

From mathieu....@gmail.com on February 23, 2011 02:07:08

Labels: -Type-Enhancement Type-Defect

@matlo
Copy link
Owner Author

matlo commented Nov 27, 2013

From mathieu....@gmail.com on February 23, 2011 02:07:31

Summary: Joystick enumeration depends on connection order

@matlo
Copy link
Owner Author

matlo commented Nov 27, 2013

From mathieu....@gmail.com on February 24, 2011 15:00:47

Status: Fixed

@matlo
Copy link
Owner Author

matlo commented Nov 27, 2013

From mathieu....@gmail.com on December 19, 2011 09:14:55

Status: Verified

@matlo matlo closed this as completed Nov 27, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant