-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
6052 customize keys and gestures #8078
Conversation
Codecov Report
@@ Coverage Diff @@
## master #8078 +/- ##
=============================================
- Coverage 32.30% 15.12% -17.19%
+ Complexity 3350 1634 -1716
=============================================
Files 352 355 +3
Lines 35803 35987 +184
Branches 4739 4772 +33
=============================================
- Hits 11567 5443 -6124
- Misses 22919 29710 +6791
+ Partials 1317 834 -483
Continue to review full report at Codecov.
|
if on the same command
moved key code vs unicode handling to Binding
Hello 👋, this PR has been opened for more than 2 months with no activity on it. If you think this is a mistake please comment and ping a maintainer to get this merged ASAP! Thanks for contributing! You have 7 days until this gets closed automatically |
Gah - I was off for February and missed this. It's fantastic in theory. I'll get it working and in if @svenmeier isn't here |
Seems great! Needs some UX work, but the UI for the key selection is fantastic. Gestures is great, but likely needs extensions The value in having different commands for the question and answers comes from requests with users with a very limited number of buttons (Bluetooth headphones for example) Ctrl+Ctrl left is a strange gesture name The defaults have been changed, which isn't ideal I'm not sure if this works with only the 9 point touch. 9 point touch divides the grid into squares, and the original touch system divides it diagonally corner to corner It's a lot of code to digest in the first commit. It'd be ideal to split this out to make it more reviewable for others I'll give this a look from a code perspective tomorrow |
Hi, I'm still watching. Thanks for your feedback. I wanted to hear opinions before working on these points:
I will rebase my code to current HEAD and work on these. |
Sorry, as it seems I won't have time to work in this in the near future. Feel free to use/reuse my proposal as you seem fit, or view it as a concept only. |
Understood, I'll use it for 2.16. Thanks for taking the time! Sorry about not getting to the initial review sooner |
Thanks a lot
It would be really useful and comfortable for BT keyboard,gamepad,remote
controller,joystick.
2021년 5월 29일 (토) 18:01, David Allison ***@***.***>님이 작성:
… Understood, I'll use it for 2.16. Thanks for taking the time!
Sorry about not getting to the initial review sooner
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8078 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATBZRFIWGKSBWDX75G6QB33TQCUONANCNFSM4W7R24ZQ>
.
|
Hello 👋, this PR has been opened for more than 2 months with no activity on it. If you think this is a mistake please comment and ping a maintainer to get this merged ASAP! Thanks for contributing! You have 7 days until this gets closed automatically |
Only hooking up and migrating gestures to go |
Hello 👋, this PR has been opened for more than 2 months with no activity on it. If you think this is a mistake please comment and ping a maintainer to get this merged ASAP! Thanks for contributing! You have 7 days until this gets closed automatically |
Keeping this one open, it's nearly at the of an odyssey of work but not done I think :-) |
Purpose / Description
Implementation of customizable keys, taking the AndroidStudios' UI for assigning keys as a role model.
Until now gestures are listed in the preferences, and each one can be configured with a viewer command. Now viewer commands are listed instead, and gestures and keys are assigned to them:
Fixes
#6052
Approach
I've joined keys and gestures into common preferences. I've thrown out the preference "gestureCornerTouch" - as soon as one corner-tap is assigned to any viewer command, corner-touches are applied.
Viewer commands are now a Enum, to make them easier to handle.
For this I had to change a lot of places, which makes this change larger than expected. I cleaned up AbstractFlashcardViewer and Reviewer by pulling out much of the gesture and key processing.
Key events are now generally handling in key-down, to be able to intercept media keys (e.g. volume-up/-down). I'm not sure why PeripheralKeymap used key-up instead.
I don't expect this to be merged right away but a basis for a solution instead.
How Has This Been Tested?
I've ran Ankidroid's test cases an tested manually on my Android device.
Note that two tests for the currently fixed peripheral keymap fail at the moment - before adjusting these I'd like to get some feedback first:
PeripheralKeymap supported different keys for the question and the answer side. That could be added here too, but personally I don't see much value in it.
Checklist
if
statements)