Repository navigation
Handle KEYCODE_DPAD_CENTER and KEYCODE_ENTER #1670
Description
http://developer.android.com/guide/topics/ui/accessibility/apps.html:
Handling directional controller clicks
On most devices, clicking a view using a directional controller sends a KeyEvent with KEYCODE_DPAD_CENTER to the view currently in focus. All standard Android views already handle KEYCODE_DPAD_CENTER appropriately. When building a custom View control, make sure this event has the same effect as touching the view on the touchscreen.
Your custom control should also treat the KEYCODE_ENTER event the same as KEYCODE_DPAD_CENTER. This approach makes interaction from a full keyboard much easier for users.
Activity
11 remaining items
mossmana commentedon Nov 6, 2023
@gspencergoog I was considering picking this issue up, but would it make sense to wait until #136419 is complete?
gspencergoog commentedon Nov 6, 2023
Well... it's up to you. That won't be "finished" for more than a year, since once it's deprecated, we need to wait a year to remove the redundant code. So this bug will be open another year before being fixed. The down side of fixing it now is that you'll probably have to fix it for both kinds of events. It's not likely to be too complicated, however.
Personally, I'd just fix it now regardless and we'll remove the redundant code when we remove the rest of it in a year.
mossmana commentedon Nov 8, 2023
I'll take a preliminary look at this issue. Tracking findings in https://docs.google.com/document/d/1Y984br0oLq2rkyQku4ve_zpR8lOeETb24ulCJN6yUls/edit?usp=sharing
Handle KEYCODE_DPAD_CENTER and KEYCODE_ENTER (#140808)
github-actions commentedon Jan 17, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.