-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Support for Home and Search media keys in TV mode #5955
Conversation
The remote I have has some extra "media" buttons besides the already supported playback controls. This adds support for "Find" button to navigate to search page and "BrowserHome" button to navigate back to main screen. Adding these to the `NavigationKeys` only enables functionality for TV mode which I think is pretty reasonable constraint - on actual desktop people might prefer to use these keys to control the browser rather than Jellyfin interface.
Quality Gate passedIssues Measures |
Cloudflare Pages deployment
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code changes look good to me. @dmitrylyzo is this something you would like to test?
Yeah, the code looks fine, but I don't know which buttons in the emulator the new codes correspond to. |
I mean, I tried all buttons in the webOS 5 emulator and didn't get these codes. Or do you mean you have some sort of universal remote connected to the TV (mini keyboard)? My main concern is the possibility of unnecessary overriding of default actions. All I can say is that Btw, there's |
Yes this is exactly my situation. I do think some "multimedia" keyboards also have some of these buttons.
Yeah some remotes have Home mapped to Meta as that is what various systems use to go to OS home screen, show start menu, etc.. I would be careful about overriding that one as it would be either captured by OS or it might prevent user from returning to OS home easily. My remote specifically has
Yes, although I think one of the remotes I had did generate
That's why the override only applies to TV interface where both |
@dmitrylyzo if you're using X11 on Linux to run your emulator, I think you can simulate the keys with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using the wireless mini-keyboard, I was able to use Home
in the browser (in TV mode).
Find
did not work (KRunner menu appeared).
In Tizen and webOS, the buttons don't work. But they are unlikely to conflict.
I think in the future we will probably have a key mapping controller - we will be able to reassign them.
Since it works for you. LGTM
The remote I have has some extra "media" buttons besides the already supported playback controls.
This adds support for "Find" button to navigate to search page and "BrowserHome" button to navigate back to main screen.
Adding these to the
NavigationKeys
only enables functionality for TV mode which I think is pretty reasonable constraint - on actual desktop people might prefer to use these keys to control the browser rather than Jellyfin interface.