forked from teamfinalmouse/xlat
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Basic keyboard support #1
Open
RockyZeroFour
wants to merge
25
commits into
main
Choose a base branch
from
feature/keyboard-support
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+1,193
−538
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
RockyZeroFour
commented
Apr 10, 2024
•
edited
Loading
edited
- new detection mode for keyboard support
- when the click or motion detection mode is selected it primarily searches for a boot mouse interface
- when the key detection mode is selected it primarily searches for a boot keyboard interface
- Prevent overflow of the next graph value - Also considers large coordinates now
- Show the same amount of data points as total ticks - This fixes the problem that only 10 data points are mapped to 11 points of the X axis - Removed the chart range for the X axis because that only apply for the scatter graph type while the bar type is used instead
Thank you for your contribution!
If we want to prescale the timer by 100, ARR needs to be set to 99.
When searching for interfaces, when a mouse isn't found, accept any interface, even if the subclass isn't "Boot". This lets us connect things like game controllers.
So that GitHub doesn't complain.
- new detection mode for keyboard support - when the click or motion detection mode is selected it primarily searches for a boot mouse interface - when the key detection mode is selected it primarily searches for a boot keyboard interface -
- Allows to select a specific interface number in which a mouse or keyboard report is searched - If set to AUTO it will search in the first corresponding boot interface
- Fix the usage of reportIDs, before one the reportID one was checked if reportIDs were used - Show the reportID of the found device
- Correct usage of the current interface number for requests - Displaying the connected device even when unsupported - Better identification if a mouse or keyboard is currently searched
- Suppress the mentioning of the word "HID" when a device is connected
- The HID interface type detection no longer falls back to a mouse if the interface protocol code is set to None instead of a moiuse or keyboard boot code - The HID event handling now only relies on the selected detection mode and if the related function was found during the parsing of the HID report descriptor
RockyZeroFour
force-pushed
the
feature/keyboard-support
branch
2 times, most recently
from
January 31, 2025 11:30
8b9f40f
to
7670db9
Compare
- Fixes the issue that a later mouse report can overwrite the keyboard report - Report ID assignment now depends on the detection mode
RockyZeroFour
force-pushed
the
feature/keyboard-support
branch
2 times, most recently
from
February 2, 2025 10:49
c0c18b9
to
7789c83
Compare
RockyZeroFour
force-pushed
the
feature/keyboard-support
branch
2 times, most recently
from
February 3, 2025 11:04
5ab01d6
to
8e96d85
Compare
- Possibility to filter for a specific report ID - Allows to select wanted report if interface has multiple reports of the same kind
RockyZeroFour
force-pushed
the
feature/keyboard-support
branch
from
February 3, 2025 11:22
8e96d85
to
4e6767a
Compare
- Separates the handling of the motion data from the button data - Allows to handle reports with buttons which don't have motion data - Enables to test gamepads
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.