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

Input configuration always opens SDL input config, despite using a different plugin #123

Open
bkacjios opened this issue Mar 29, 2018 · 4 comments

Comments

@bkacjios
Copy link

I'm currently developing an input plugin for mupen, and I just recently found that the configure button, under the plugin settings menu, always opens up the config for the SDL plugin. Would it be possible to have it open the auto generated config window instead, like any other plugin type?

@gen2brain
Copy link
Member

It is probably possible, but there are some hardcoded code for input config, will need to check. Are there any other input plugin for Linux currently that I can use to to test, beside default one?

@bkacjios
Copy link
Author

Well, I literally just finished one yesterday that you could use to test with.

https://github.com/bkacjios/n64-input-plugin-serial/releases

@bsmiles32
Copy link
Member

There is also the raphnet plugin:

https://github.com/raphnet/mupen64plus-input-raphnetraw

@gen2brain
Copy link
Member

As written in the linked issue:

The goal is to implement one input plugin, that will work for them all. The same is currently for all other plugin types. The reason why m64py is still usable after all these years is because of that, e.g. GLideN64 didn't exist back then, but you could change settings from m64py as soon as it was out (options are not grouped or sorted but it works).
That needs to be done also for the input plugin, and it is the highest priority for me, I just don't have the time, but eventually, I will get to it. Any help is welcomed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants