Apex 4 integration #6
Open
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.
Hello,
First of all thank you for doing the hard work here.
What I originally wanted was to support adaptive trigger commands, but that doesn’t really work while the stock
xpaddriver is bound to the device, since it blocks sending vendor-specific commands. Because of that, I ended up patchingxpadto expose Flydigi’s output interface instead: https://github.com/RezenDeveloper/xpad_flydigiEven though adaptive triggers still don’t work with
flydigictl, I was able to add:xpadreload fallback (don´t know why but the default one wasn't working for me)I’m not 100% sure how the trigger commands behave on other Flydigi controllers, so for now I limited them to Apex 4 only to be safe.