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

[TEST] Change keyboard inputs to send processed bitmap to the keyboard interface #170

Open
DanielMolina24 opened this issue Jan 18, 2021 · 1 comment
Assignees
Labels
good-first-issue Good issues for incoming members low-priority Issues that aren't important and don't change the code outcomes
Milestone

Comments

@DanielMolina24
Copy link
Contributor

Per @AVSurfer123's suggestion, we want to change the keyboard inputs script to not only record the keys being pressed, but also process them so when they are received by the keyboard_interface, it can just be passed into send_user_inputs without the need to process what keyboard_interface sent. Doing this might mean we can get rid of the keyboard_interface entirely and have net_handler open a separate socket to communicate with the keyboard_inputs script, since the keyboard_interface was mainly in charge of processing what it received from the python script. The python script would have to utilize the python library ctypes: https://stackoverflow.com/questions/19716315/how-to-create-a-fixed-size-unsigned-integer-in-python
Marking as low feature for now since what we have works fine, but would definitely reduce the middlemen factors here

@DanielMolina24 DanielMolina24 added the low-priority Issues that aren't important and don't change the code outcomes label Jan 18, 2021
@DanielMolina24
Copy link
Contributor Author

DanielMolina24 commented Jan 21, 2021

C-Types package:
https://docs.python.org/3/library/ctypes.html

@DanielMolina24 DanielMolina24 added this to the 1.2 milestone Jan 21, 2021
@AVSurfer123 AVSurfer123 added the good-first-issue Good issues for incoming members label Sep 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good-first-issue Good issues for incoming members low-priority Issues that aren't important and don't change the code outcomes
Projects
None yet
Development

No branches or pull requests

5 participants