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.

Sign up for GitHub

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

Jump to bottom

Can’t bind to Push in Windows #64

Closed
brunchboy opened this issue Jun 9, 2016 · 1 comment
Closed

Can’t bind to Push in Windows #64

brunchboy opened this issue Jun 9, 2016 · 1 comment
Assignees
@brunchboy
Labels
bug

Comments

@brunchboy
Copy link
Member

brunchboy commented Jun 9, 2016 •
edited
Loading

The user port names don’t match. Not even updating the regular expression used in the binding code helps, because the input and output ports have names that differ from each other, and the surrounding code assumes it can find the output port by looking for a port with the same name and description as the input port.

To solve this the identification of the right output port is going to have to be moved into the recognizer function for each controller implementation, and be one of the values that the recognizer returns.
@brunchboy brunchboy added the bug label Jun 9, 2016
@brunchboy brunchboy self-assigned this Jun 9, 2016
@brunchboy
Copy link
Member Author

Similar issues apply to the LaunchPad Pro, but the same fix will work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brunchboy brunchboy

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brunchboy