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

Clean-up input subsystem #309

Closed
ataffanel opened this issue Jul 26, 2017 · 2 comments
Closed

Clean-up input subsystem #309

ataffanel opened this issue Jul 26, 2017 · 2 comments

Comments

@ataffanel
Copy link
Member

Currently the input subsystem is complex and spread all around the client. This makes it very hard to implement new control mode in the client and to use the input subsystem in other programs.

The input subsystem should be revamped to be more self-contained and so to make it easier to work with it.

@Mitteau
Copy link
Contributor

Mitteau commented Apr 6, 2018

I am working on issue #192 and I completely agree with this commit. I think there are three ways to revamp the system:
1/ isolate blocks of lines in the main.py (and others modules concerned), the simplest way. I use it presently,
2/ create a new file which contains every declaration an function concerned and "include" it (import) in the main.py and others,
9/ create a new class dealing with everything which concerns input suystem (but is that not the aim of the class JoystickReader?).
What do you think is the best way?
BR Jean-Claude

@jonasdn
Copy link
Contributor

jonasdn commented Mar 9, 2021

Is this issue still valid? @ataffanel @Mitteau ?

@jonasdn jonasdn closed this as completed Aug 12, 2021
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